You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Siddharth Wagle (Jira)" <ji...@apache.org> on 2019/10/01 02:43:00 UTC

[jira] [Updated] (RATIS-693) Combine notifyLeader and notifyLeaderChanged calls on StateMachine

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

Siddharth Wagle updated RATIS-693:
----------------------------------
    Attachment: RATIS-693.02.patch

> Combine notifyLeader and notifyLeaderChanged calls on StateMachine
> ------------------------------------------------------------------
>
>                 Key: RATIS-693
>                 URL: https://issues.apache.org/jira/browse/RATIS-693
>             Project: Ratis
>          Issue Type: Improvement
>          Components: raft-group, server
>    Affects Versions: 0.5.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Major
>             Fix For: 0.5.0
>
>         Attachments: RATIS-693.01.patch, RATIS-693.02.patch
>
>
> RATIS-678 introcuded _notifyLeaderChanged_ API on the StateMachine interface which will be called to notify the statemachine when the leaderId changes on leader as well as the follower.
> Downstream services like Ozone utilize this functionality to decide when the Raft group is ready to accept writes and do open the write pipeline.
> Purpose of this jira is to combine notifyLeader and notifyLeaderChanged into a single API.



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