[IGNITE-15083] Implement leaseholder selection and failover

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Labels: iep-61 ignite-3
• Epic Link: Ignite 3 transactions
• Assignee: Unassigned
• Reporter: Alexey Scherbakov
• Created: 09/Jul/21 07:57
• Updated: 29/Nov/23 07:37
• Resolved: 29/Nov/23 07:37

Description

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 is used for lock requests processing.
• 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.

Issue Links

• duplicates: IGNITE-18856 Switch primary replica calls from Raft leader to primary replica
• is duplicated by: IGNITE-17256 Introduce lease-based engine for primary replica stability (primary replica selection and failover)