You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by cutd <cu...@foxmail.com> on 2017/04/05 08:10:22 UTC

NimbusLeaderNotFoundException Bug

First of all,I think this is a bug that can't access nimbus when a topology is active in the cluster then update storm nimbus version.In my opinion,the data(jar,conf...) of remote activity topology not in local new nimbus directory so that zookeeper think this new nimbus not a leader and do nothing.And then access Storm UI will see that "org.apache.storm.utils.NimbusLeaderNotFoundException: Could not find leader nimbus from seed hosts ["master"]. Did you specify a valid list of nimbus hosts for config nimbus.seeds?" 

The nimbus log is :

2017-04-05 15:53:47.873 o.a.s.s.o.a.c.f.i.CuratorFrameworkImpl timer [INFO] Starting
2017-04-05 15:53:47.873 o.a.s.s.o.a.z.ZooKeeper timer [INFO] Initiating client connection, connectString=zk-03:2181,zk-01:2181,zk-02:2181/storm sessionTimeout=20000 watcher=org.apache.storm.shade.org.apache.curator.ConnectionState@7c95804f
2017-04-05 15:53:47.875 o.a.s.s.o.a.z.ClientCnxn timer-SendThread(zk-01:2181) [INFO] Opening socket connection to server 10.25.142.16/zk-01:2181. Will not attempt to authenticate using SASL (unknown error)
2017-04-05 15:53:47.876 o.a.s.s.o.a.z.ClientCnxn timer-SendThread(zk-01:2181) [INFO] Socket connection established to 10.25.142.16/zk-01:2181, initiating session
2017-04-05 15:53:47.879 o.a.s.s.o.a.z.ClientCnxn timer-SendThread(zk-01:2181) [INFO] Session establishment complete on server 10.25.142.16/zk-01:2181, sessionid = 0x258f0f7a42bf9fc, negotiated timeout = 20000
2017-04-05 15:53:47.881 o.a.s.s.o.a.z.ZooKeeper timer [INFO] Session: 0x258f0f7a42bf9fc closed
2017-04-05 15:53:47.882 o.a.s.s.o.a.z.ClientCnxn timer-EventThread [INFO] EventThread shut down
2017-04-05 15:53:47.882 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:53:47.882 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:53:57.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:53:57.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:54:07.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:54:07.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:54:17.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:54:17.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:54:27.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:54:27.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:54:37.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:54:37.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:54:47.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:54:47.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:54:57.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:54:57.883 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup
2017-04-05 15:55:07.885 o.a.s.d.nimbus timer [INFO] not a leader, skipping assignments
2017-04-05 15:55:07.885 o.a.s.d.nimbus timer [INFO] not a leader, skipping cleanup



The storm.yaml is :
storm.zookeeper.servers:
    - "zk-03"
    - "zk-01"
    - "zk-02"
storm.local.hostname: "master"
nimbus.seeds: ["master"]




Maybe I should copy data of remote activity topollogy to the new storm ,but I don't know how because I had deleted the old one .