You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/04/13 12:17:12 UTC

[GitHub] [shardingsphere-elasticjob] denvensss opened a new issue #1871: Is it feasible to replace zookeeper with consult

denvensss opened a new issue #1871:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1871


   Is it feasible to replace zookeeper with consult? Can you tell me how to operate?
   MySQL is used for data storage, and the project can register with the consul instead of zookeeper 


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] yuanrengu commented on issue #1871: Is it feasible to replace zookeeper with consult

Posted by GitBox <gi...@apache.org>.
yuanrengu commented on issue #1871:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1871#issuecomment-821746986


   Being more foundational, architectural elements are harder to  replace. I don't think it's a good idea to replace zk with cousul.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1871: Is it feasible to replace zookeeper with consult

Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1871:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1871#issuecomment-818795583


   The ElasticJob makes full use of features of Zookeeper such as ephemeral nodes, watches. I don't think is easy to replace Zookeeper with Consul.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org