Support Questions
Find answers, ask questions, and share your expertise

metron indexing fail right after it start

metron indexing fail right after it start

dfsIndexingBolt --LOCAL_OR_SHUFFLE--> indexingErrorBolt
--------------------------------------
4543 [main] INFO  o.a.s.f.Flux - Running remotely...
4544 [main] INFO  o.a.s.f.Flux - Deploying topology in an ACTIVE state...
4587 [main] INFO  o.a.s.StormSubmitter - Generated ZooKeeper secret payload for MD5-digest: -6007092214841415612:-7169112016178865033
4721 [main] INFO  o.a.s.s.a.AuthUtils - Got AutoCreds []
Exception in thread "main" java.lang.RuntimeException: Topology with name `batch_indexing` already exists on cluster
    at org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:234)
    at org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:310)
    at org.apache.storm.flux.Flux.runCli(Flux.java:171)
    at org.apache.storm.flux.Flux.main(Flux.java:98)

Command failed after 1 tries
1 REPLY 1

Re: metron indexing fail right after it start

Super Collaborator

Looks like this topology is already running per the log:

Exception in thread "main" java.lang.RuntimeException: Topology with name `batch_indexing` already exists on cluster

You can run storm list to check if the topology is running and if it is, then run storm kill batch_indexing to terminate the existing one and restart indexing topology