isHuangXin commented on issue #24869:
URL: 
https://github.com/apache/shardingsphere/issues/24869#issuecomment-1486080349

   - This is my server.yaml
   - I found that when using cluster mode, shardingsphere cannot connect to my 
local zookeeper correctly, I will fix this bug first
   
   
![image](https://user-images.githubusercontent.com/57054352/228103124-cf49863f-78a1-4acc-b143-c638dbce64c3.png)
   
   
![image](https://user-images.githubusercontent.com/57054352/228103145-fd418bea-fd7e-4b3e-9c38-c26400abf3ae.png)
   
   - zookeeper connection error log
   
   `Exception in thread "main" 
org.apache.shardingsphere.mode.repository.cluster.exception.ClusterPersistRepositoryException:
 Cluster persist repository error, reason is: KeeperErrorCode = OperationTimeout
        at 
org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.ZookeeperExceptionHandler.handleException(ZookeeperExceptionHandler.java:53)
        at 
org.apache.shardingsphere.mode.repository.cluster.zookeeper.ZookeeperRepository.initCuratorClient(ZookeeperRepository.java:124)
        at 
org.apache.shardingsphere.mode.repository.cluster.zookeeper.ZookeeperRepository.init(ZookeeperRepository.java:77)
        at 
org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.getClusterPersistRepository(ClusterContextManagerBuilder.java:68)
        at 
org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:49)
        at 
org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.createContextManager(BootstrapInitializer.java:69)
        at 
org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:59)
        at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:54)`
   


-- 
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