All these are info logs and I don¹t see any errors. You need to provide some additional logs showing app errors and the slider-agent log to be able to debug further.
-Gour On 12/22/16, 7:31 PM, "sun ww" <spe...@outlook.com> wrote: >Hi > I'm using slider0.8 to deploy a storm0.10 cluster. When Nimbus >recover after abnormal, the new Nimbus can't become a leader. Is I >miss something. Thanks. > This is Nimbus log: >b.s.d.nimbus [INFO] not a leader, skipping assignments >b.s.d.nimbus [INFO] not a leader, skipping cleanup >b.s.d.nimbus [INFO] not a leader skipping , credential renweal. >b.s.zookeeper [INFO] leader latch is not started so no >removeFromLeaderLockQueue needed. >b.s.d.nimbus [INFO] missing topology test-topology1-1-1472033042 has >state on zookeeper but doesn't have a local dir on this host. >b.s.d.nimbus [INFO] trying to download missing topology code from >b.s.zookeeper [INFO] LeaderLatch was in closed state. Resetted the >leaderLatch and listeners. >b.s.zookeeper [INFO] Queued up for leader lock. >b.s.zookeeper [INFO] dcp14 gained leadership, checking if it has all the >topology code locally. >b.s.zookeeper [INFO] active-topology-ids [test-topology1-1-1472033042] >local-topology-ids [] diff-topology [test-topology1-1-1472033042] >b.s.zookeeper [INFO] code for all active topologies not available >locally, giving up leadership. >b.s.d.nimbus [INFO] not a leader, skipping assignments >b.s.d.nimbus [INFO] not a leader, skipping cleanup >b.s.d.nimbus [INFO] not a leader, skipping assignments >b.s.d.nimbus [INFO] not a leader, skipping cleanu >
