DarkAssassinator commented on issue #12516:
URL: 
https://github.com/apache/dolphinscheduler/issues/12516#issuecomment-1291918313

   hi @luckyboy2226, please check the following root causes.
   **1. Why DS will throw this exception?**
   A: Becuase you're using the wrong combination of `Zookpeeper` in combination 
with `Curator`. And ZooKeeper 3.4.x is now at EOL. And the latest versions of 
Curator have removed support for it. So i suggest that u should update your zk 
version or you should pin to version 4.2.x of Curator. Curator 4.2.x supports 
ZooKeeper 3.4.x ensembles in a soft-compatibility mode. For more details, 
please refer to [ZooKeeper Version 3.4.x 
Compatibility](https://curator.apache.org/zk-compatibility-34.html)
   > DS Curator version: 5.3.0
   > Your ZK version: 3.4.6
   
   **2. Why zookeeper rootpath still is `dolphinscheduler` after u modify the 
${zkRoot:-"/dolphinschedulerV310"} ?**
   A: becasue u should change the `registry.zookeeper.namespace` in yml. DS did 
not use  `${zkRoot}` to create the namspace.
   
![image](https://user-images.githubusercontent.com/20518339/198019430-44302fc2-e190-48f7-acd5-7a052427029f.png)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to