[IGNITE-18744] Implement primary replica side leaseGrant handler

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: iep-101 ignite-3
• Epic Link: Placement Driver [Part 1]
• Assignee: Denis Chudov
• Reporter: Alexander Lapin
• Reviewer: Vladislav Pyatkov
• Created: 07/Feb/23 13:29
• Updated: 04/Sep/24 16:19
• Resolved: 27/Mar/23 08:16

Description

Motivation

Primary replica candidate should properly handle leaseGrant message. In case of RAFT following steps are expected:

• After receiving leaseGrant(force = false) message primary replica candidate (the one that have received the message) should check whether group is ready (meaning that leader is elected) or await leader election. So, reactive communication is expected here.
• On leader election or on leader detection:
  • if leader isn't collocated with primary replica candidate, primary replica candidate should send leaseGrantResp that assumes primary replica redirect.
  • send leaseGrantResp[OK]

Definition of Done

• PD retrieves leaseGranted

 

Issue Links

• is blocked by: IGNITE-19014 Topology aware Raft client creates its own message handler which is not aware of Raft group
• links to: PR