[jira] [Updated] (STORM-1115) Stale leader-lock key effectively bans all nodes from becoming leaders
[ https://issues.apache.org/jira/browse/STORM-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Kellogg updated STORM-1115: Component/s: storm-core > 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 > Components: storm-core >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)
[jira] [Updated] (STORM-1115) Stale leader-lock key effectively bans all nodes from becoming leaders
[ https://issues.apache.org/jira/browse/STORM-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated STORM-1115: --- Assignee: Daniel Schonfeld > 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 > > 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)
[jira] [Updated] (STORM-1115) Stale leader-lock key effectively bans all nodes from becoming leaders
[ https://issues.apache.org/jira/browse/STORM-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Schonfeld updated STORM-1115: Description: 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() was: I believe this curator bug is what's in play causing the above described situation. https://issues.apache.org/jira/browse/CURATOR-202 > 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 > > 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)
