You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2023/05/18 08:43:00 UTC

[jira] [Updated] (IGNITE-18744) Implement primary replica side leaseGrant handler

     [ https://issues.apache.org/jira/browse/IGNITE-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin updated IGNITE-18744:
-----------------------------------------
    Labels: iep-101 ignite-3  (was: ignite-3)

> Implement primary replica side leaseGrant handler
> -------------------------------------------------
>
>                 Key: IGNITE-18744
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18744
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Assignee: Denis Chudov
>            Priority: Major
>              Labels: iep-101, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> h3. 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]
> h3. Definition of Done
>  * PD retrieves leaseGranted
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)