Invalid cluster setup, missing znode path, Cluster structure is not set up for cluster
See original GitHub issueHI everyone, I’m using code from commit hash 70ac340 master branch. Now i setting
- 1 Controller with resource : 500m CPU , 1500m memory
- 4 Worker with resource : 100m CPU, 1000m memory
1 Controller & 3 Worker is good now, but the last Worker through this exception : Anyone explain clear for me?. @Technoboy- @yangy0000 do you know this ?
[2019-11-05 10:41:40,518] INFO Waiting for keeper state SyncConnected (org.I0Itec.zkclient.ZkClient:936)
[2019-11-05 10:41:40,518] INFO Handling new session, session id: 1062cda1558000f, instance: HelixMirrorMaker-1572950499885, instanceTye: PARTICIPANT, cluster: uReplicatorTEST, zkconnection: State:CONNECTED Timeout:30000 sessionid:0x1062cda1558000f local:/172.16.129.24:52794 remoteserver:10.100.3.101/10.100.3.101:2181 lastZxid:0 xid:1 sent:1 recv:1 queuedpkts:0 pendingresp:0 queuedevents:0 (org.apache.helix.manager.zk.ZKHelixManager:748)
[2019-11-05 10:41:40,518] WARN ParticipantHealthReportTimerTask already stopped (org.apache.helix.healthcheck.ParticipantHealthReportTask:67)
[2019-11-05 10:41:40,644] INFO Invalid cluster setup, missing znode path: /uReplicatorTEST/CONTROLLER
Invalid cluster setup, missing znode path: /uReplicatorTEST/CONTROLLER/MESSAGES
Invalid cluster setup, missing znode path: /uReplicatorTEST/CONTROLLER/ERRORS
Invalid cluster setup, missing znode path: /uReplicatorTEST/CONTROLLER/STATUSUPDATES
Invalid cluster setup, missing znode path: /uReplicatorTEST/CONTROLLER/HISTORY
(org.apache.helix.manager.zk.ZKUtil:88)
2019-11-05T10:41:40.653+0000: Total time for which application threads were stopped: 0.0015168 seconds, Stopping threads took: 0.0000388 seconds
[2019-11-05 10:41:40,645] ERROR fail to createClient. (org.apache.helix.manager.zk.ZKHelixManager:496)
org.apache.helix.HelixException: Cluster structure is not set up for cluster: uReplicatorTEST
at org.apache.helix.manager.zk.ZKHelixManager.handleNewSession(ZKHelixManager.java:861)
at org.apache.helix.manager.zk.ZKHelixManager.createClient(ZKHelixManager.java:493)
at org.apache.helix.manager.zk.ZKHelixManager.connect(ZKHelixManager.java:531)
at kafka.mirrormaker.WorkerInstance.addToHelixController(WorkerInstance.scala:340)
at kafka.mirrormaker.WorkerInstance.start(WorkerInstance.scala:250)
at kafka.mirrormaker.MirrorMakerWorker.main(MirrorMakerWorker.scala:109)
at com.uber.stream.kafka.mirrormaker.starter.MirrorMakerStarter.main(MirrorMakerStarter.java:44)
[2019-11-05 10:41:40,661] ERROR fail to connect HelixMirrorMaker-1572950499885 (org.apache.helix.manager.zk.ZKHelixManager:534)
org.apache.helix.HelixException: Cluster structure is not set up for cluster: uReplicatorTEST
at org.apache.helix.manager.zk.ZKHelixManager.handleNewSession(ZKHelixManager.java:861)
at org.apache.helix.manager.zk.ZKHelixManager.createClient(ZKHelixManager.java:493)
at org.apache.helix.manager.zk.ZKHelixManager.connect(ZKHelixManager.java:531)
at kafka.mirrormaker.WorkerInstance.addToHelixController(WorkerInstance.scala:340)
at kafka.mirrormaker.WorkerInstance.start(WorkerInstance.scala:250)
at kafka.mirrormaker.MirrorMakerWorker.main(MirrorMakerWorker.scala:109)
at com.uber.stream.kafka.mirrormaker.starter.MirrorMakerStarter.main(MirrorMakerStarter.java:44)
[2019-11-05 10:41:40,687] INFO Is not shutting down; call cleanShutdown() (kafka.mirrormaker.WorkerInstance:66)
[2019-11-05 10:41:40,688] INFO Start clean shutdown. (kafka.mirrormaker.WorkerInstance:66)
[2019-11-05 10:41:40,692] INFO Flushing last batches and commit offsets. (kafka.mirrormaker.WorkerInstance:66)
[2019-11-05 10:41:40,692] INFO Flushing producer. (kafka.mirrormaker.WorkerInstance:66)
Exception in thread "main" java.lang.NullPointerException
at kafka.mirrormaker.WorkerInstance.maybeFlushAndCommitOffsets(WorkerInstance.scala:346)
at kafka.mirrormaker.WorkerInstance.cleanShutdown(WorkerInstance.scala:385)
at kafka.mirrormaker.WorkerInstance$WorkerZKHelixManager.disconnect(WorkerInstance.scala:328)
at org.apache.helix.manager.zk.ZKHelixManager.connect(ZKHelixManager.java:535)
at kafka.mirrormaker.WorkerInstance.addToHelixController(WorkerInstance.scala:340)
at kafka.mirrormaker.WorkerInstance.start(WorkerInstance.scala:250)
at kafka.mirrormaker.MirrorMakerWorker.main(MirrorMakerWorker.scala:109)
at com.uber.stream.kafka.mirrormaker.starter.MirrorMakerStarter.main(MirrorMakerStarter.java:44)
2019-11-05T10:41:41.654+0000: Total time for which application threads were stopped: 0.0003464 seconds, Stopping threads took: 0.0000637 seconds
2019-11-05T10:41:42.320+0000: Total time for which application threads were stopped: 0.0006129 seconds, Stopping threads took: 0.0000342 seconds
2019-11-05T10:41:43.325+0000: Total time for which application threads were stopped: 0.0001109 seconds, Stopping threads took: 0.0000327 seconds
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Error on participant while joining cluster-Apache Mail Archives
THe cluster is setup and a controller has already connected to it. ... HelixException: Initial cluster structure is not set up for instance: ......
Read more >Cluster structure is not set up for cluster
Dears. I have the next problem, the cluster in the jboss brms and helix don´t start the service helix have this error.
Read more >Re: Error on participant while joining cluster - Varun Sharma
First make sure under /<CLUSTER_NAME>/LIVEINSTANCES/, the node you want to remove from the cluster is not running. Then you can simply remove ...
Read more >Known Issues in MapReduce and YARN | CDP Private Cloud
When the Job ACL feature is enabled using Cloudera Manager (YARN > Configuration > Enablg JOB ACLproperty), the mapreduce.cluster.acls.enabled property is not ......
Read more >org.apache.helix.PropertyPathBuilder Java Examples
isClusterSetup (clusterName, _zkClient)) { throw new HelixException("cluster " + clusterName + " is not setup yet"); } String instanceConfigsPath ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
and using worker-3.0 is recommended
restart the last worker can resolve the problem. the best order to start cluster : start controllers first, then workers。the controllers have the ability to setup the cluster info