You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Simon Cooper (JIRA)" <ji...@apache.org> on 2018/04/23 12:00:00 UTC
[jira] [Created] (STORM-3038) 'not a leader' exception submitting
topologies to LocalCluster
Simon Cooper created STORM-3038:
-----------------------------------
Summary: 'not a leader' exception submitting topologies to LocalCluster
Key: STORM-3038
URL: https://issues.apache.org/jira/browse/STORM-3038
Project: Apache Storm
Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Simon Cooper
In our local tests running on our openstack build servers, we get intermittent failures due to the following exception being thrown when submitting topologies to LocalCluster:
{code}275354 [main] WARN o.a.s.d.nimbus - Topology submission exception. (topology name='AnalyseUpdate') #error {
:cause not a leader, current leader is NimbusInfo{host='<hostname>', port=6627, isLeader=true}
:via
[{:type java.lang.RuntimeException
:message not a leader, current leader is NimbusInfo{host='<hostname>', port=6627, isLeader=true}
:at [org.apache.storm.daemon.nimbus$is_leader doInvoke nimbus.clj 150]}]
:trace
[[org.apache.storm.daemon.nimbus$is_leader doInvoke nimbus.clj 150]
[clojure.lang.RestFn invoke RestFn.java 410]
[org.apache.storm.daemon.nimbus$mk_reified_nimbus$reify__10799 submitTopologyWithOpts nimbus.clj 1681]
[org.apache.storm.daemon.nimbus$mk_reified_nimbus$reify__10799 submitTopology nimbus.clj 1774]
[sun.reflect.GeneratedMethodAccessor299 invoke nil -1]
[sun.reflect.DelegatingMethodAccessorImpl invoke DelegatingMethodAccessorImpl.java 43]
[java.lang.reflect.Method invoke Method.java 498]
[clojure.lang.Reflector invokeMatchingMethod Reflector.java 93]
[clojure.lang.Reflector invokeInstanceMethod Reflector.java 28]
[org.apache.storm.testing$submit_local_topology invoke testing.clj 310]
[org.apache.storm.LocalCluster$_submitTopology invoke LocalCluster.clj 49]
[org.apache.storm.LocalCluster submitTopology nil -1]{code}
(note that {{isLeader=true}} in the exception message)
This is despite a retry mechanism we've implemented; this seems to be a continual failure, once its hit. This tends to be surrounded by lots of zookeeper connection lost/reconnection log message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)