You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2021/07/09 07:58:00 UTC

[jira] [Created] (IGNITE-15083) Implement leaseholder selection and failover

Alexey Scherbakov created IGNITE-15083:
------------------------------------------

             Summary: Implement leaseholder selection and failover
                 Key: IGNITE-15083
                 URL: https://issues.apache.org/jira/browse/IGNITE-15083
             Project: Ignite
          Issue Type: Task
            Reporter: Alexey Scherbakov
             Fix For: 3.0.0-alpha3


The tx design [1] assumes the presence of leaseholder (stronger form of a leader) for each partition raft group.

* Leaseholder is used for reads without majority heartbeat
* Leaseholder for lock acquisition.
* Only one leaseholder should exists at a time.
* Leaseholders map is stored in metastore (can be discovered by asking group members in the first approach)
* Tx coordinators are subscribed for leaseholder status updates.

The lease acquisiotion implementation details are open for now [2]. 
Jraft includes expiration based leases (similar to yugabyte's), and this should be enough for the first approach.

[1] https://github.com/apache/ignite-3/tree/main/modules/transactions
[2] Cocroach and tikv use raft log based approach.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)