[jira] [Resolved] (STORM-1115) Stale leader-lock key effectively bans all nodes from becoming leaders

["Robert Joseph Evans (JIRA)" <ji...@apache.org>]

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

Robert Joseph Evans resolved STORM-1115.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0

Thanks [~danielschonfeld],

I merged this into master.  Keep up the good work.

> Stale leader-lock key effectively bans all nodes from becoming leaders
> ----------------------------------------------------------------------
>
>                 Key: STORM-1115
>                 URL: https://issues.apache.org/jira/browse/STORM-1115
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.11.0
>            Reporter: Daniel Schonfeld
>            Assignee: Daniel Schonfeld
>             Fix For: 0.11.0
>
>
> I believe this curator bug is what's in play causing the above described situation.
> https://issues.apache.org/jira/browse/CURATOR-202
> Whenever we were hit by this bug we'd start seeing problems in submitting topologies to nimbus, as well as having problems activating/deactivating/killing topologies.  Basically any topology that utilizes the `is-leader` macro, since no nimbus believes itself to be the leader based on LeaderLatch.hasLeadership()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)