Created on 09-06-2018 12:54 AM - edited 08-18-2019 01:26 AM
Metron Indexing Service Will Not Start
3524 [main] INFO o.a.s.f.Flux - Running remotely...
3524 [main] INFO o.a.s.f.Flux - Deploying topology in an ACTIVE state...
3559 [main] INFO o.a.s.StormSubmitter - Generated ZooKeeper secret payload for MD5-digest: -7710268567444301830:-7594470148367190707
3752 [main] INFO o.a.s.u.NimbusClient - Found leader nimbus : hdp01-ib.hpc.lan:6627
3772 [main] INFO o.a.s.s.a.AuthUtils - Got AutoCreds []
3775 [main] INFO o.a.s.u.NimbusClient - Found leader nimbus : hdp01-ib.hpc.lan:6627
Exception in thread "main" java.lang.RuntimeException: Topology with name `random_access_indexing` already exists on cluster
at org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:240)
at org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:390)
at org.apache.storm.flux.Flux.runCli(Flux.java:171)
at org.apache.storm.flux.Flux.main(Flux.java:98)
2018-08-29 08:17:27,329 - Skipping stack-select on METRON because it does not exist in the stack-select package structure.
Dashboard image showing installed services attached
Created 09-06-2018 01:09 AM
Hi @Joel Hatcher,
as the exception indicates topology already exists why dont you go kill the topology and try to start it again.
the syntax for storm CLI will be
storm kill topology-name [-w wait-time-secs]
Created 09-06-2018 01:09 AM
Hi @Joel Hatcher,
as the exception indicates topology already exists why dont you go kill the topology and try to start it again.
the syntax for storm CLI will be
storm kill topology-name [-w wait-time-secs]
Created 09-06-2018 01:43 PM
That fixed the startup, but ambari still show it as not running. The storm ui shows that it is running, but it does not appear to be bug Ambari-1451 as I already have requests version 2.6.1 installed. Any ideas? Thank you for your help.ambari-agent.txt
Created 09-07-2018 05:47 AM
Hi @Joel Hatcher ,
Glad that metron is started now.
Can you please accept the answer so that it will help other community users to understand the correct answer.
and for your Ambari showing wrong Metron status, can you confirm whats status in ambari-server.log , attached ambari-agent gives no data about the status .
you can check in ambari-server.log and look out for log's from class
ServiceResourceProvider
Created 09-07-2018 01:37 PM
The ambari server log indicates that indexing is running.
06 Sep 2018 14:49:35,355 INFO [ambari-heartbeat-processor-0] ServiceComponentHostImpl:1039 - Host role transitioned to a new state, serviceComponentName=METRON_INDEXING, hostName=hdp04-ib.hpc.lan, oldState=STARTING, currentState=STARTED