Zookeeper was created because fault-tolerant algorithms are extremely hard to test and get correct. Maybe the hardest thing in computing. Using a trusted implementation frees up lots of developer time.
To get an idea of the difficulty, read through the kinds of things fixed in the Zookeeper release notes. https://zookeeper.apache.org/releases.html Elasticsearch does not have a good record on fault-tolerance. I haven’t checked recently, but it was losing updates during leader elections for several years worth of software releases. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jun 9, 2020, at 12:37 PM, David Hastings <hastings.recurs...@gmail.com> > wrote: > > Zookeeper is annoying to both set up and manage, but then again the same > thing can be said about solr cloud. not certain why you would want to deal > with either > > On Tue, Jun 9, 2020 at 3:29 PM S G <sg.online.em...@gmail.com> wrote: > >> Hello, >> >> I recently stumbled across KIP-500: Replace ZooKeeper with a Self-Managed >> Metadata Quorum >> < >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum >>> >> Elastic-search does this too. >> And so do many other systems. >> >> Is there some work to go in this direction? >> It would be nice to get rid of another totally disparate system. >> Hardware savings would be nice to have too. >> >> Best, >> SG >>
