[GitHub] [pulsar] IsNull edited a comment on issue #572: Don't depend on ZooKeeper for coordination

[GitBox <gi...@apache.org>]

IsNull edited a comment on issue #572: Don't depend on ZooKeeper for coordination
URL: https://github.com/apache/pulsar/issues/572#issuecomment-614706722
 
 
   When I stumbled upon Plusar I died twice. First I read the description and, coming from a Kafka / Kubernetes background, I thought man these guys really tick everything I could wish for. After that, I clicked the Docs page and when I discovered those nasty ZK boxes in the diagram the dream died as fast as it was emerging.
   
   I can understand the argument of not repeating yourself and it may look like a good idea to have that complicated quorum stuff sorted out with a separate microservice (ZK). However, If you produce the situation that the state of multiple services are interconnected and can desynchronize, its an operational nightmare. At least in a containerised and managed environment like Kubernetes.
   
   Kafka has (finally) accepted this reality and is moving away from an external solution to embed quorum ([KIP-500](https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum)). By having the Quorum State and Broker Data state in the same location, desynchronisation are no longer possible and operations are very much simplified.
   
   So my two cents would be, to not make ZK replaceable by something other, but instead remove the need for an external solution altogether. 

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


With regards,
Apache Git Services