[jira] [Resolved] (RATIS-18) A new leader should start serving client requests only after it commits the first leader-placeholder entry

["Jing Zhao (JIRA)" <ji...@apache.org>]

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

Jing Zhao resolved RATIS-18.
----------------------------
       Resolution: Fixed
    Fix Version/s: 0.1

Thanks for the review, Nicholas and Enis! I've committed the patch.

> A new leader should start serving client requests only after it commits the first leader-placeholder entry
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: RATIS-18
>                 URL: https://issues.apache.org/jira/browse/RATIS-18
>             Project: Ratis
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>             Fix For: 0.1
>
>         Attachments: RATIS-18.000.patch, RATIS-18.001.patch
>
>
> When a raft peer becomes the new leader, it can commit entries belonging to the previous term only along with the entry with the new term. Before that commit happens, the new leader cannot determine exactly what entries should be applied to the state machine and the retry cache. The retry cache is complete only after the leader commits the first leader-placeholder entry.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)