You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2018/01/12 19:27:05 UTC

[jira] [Updated] (SAMZA-1166) Leader should hold a lock to avoid failures on long GC pause/timeouts

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

Jake Maes updated SAMZA-1166:
-----------------------------
    Fix Version/s:     (was: 0.14.0)
                   0.15.0

> Leader should hold a lock to avoid failures on long GC pause/timeouts
> ---------------------------------------------------------------------
>
>                 Key: SAMZA-1166
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1166
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>             Fix For: 0.15.0
>
>
> The standard leader election algorithm works well for the leader election. However, for the leader to maintain its leadership, it needs a way to identify that it is still the leader. This check should happen before each "leader" like operation. A simple way to do this is to treat leadership as a resource and use a lock. Only operate as leader when lock is held by self. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)