We have just done an upgrade of ZK to 3.3.0. Previous to this, ZK has been
up for about a year with no problems.
On two nodes, we killed the previous instance and started the 3.3.0
instance. The first node was a follower and the second a leader.
All went according to plan and no clients seemed
I can't comment on the details of your code (but I have run in-process ZK's
in the past without problem)
Operationally, however, this isn't a great idea. The problem is two-fold:
a) firstly, somebody would probably like to look at Zookeeper to understand
the state of your service. If the
There are a small handful of cases where the server code will
system.exit. This is typically only if quorum communication fails in
some weird, unrecoverable way. We've been working to remove this (mainly
so zk can be deployed in a container) but there are still a few cases left.
I don't see
Ok, I think this is possible.
So here is what happens currently. This has been a long standing bug and
should be fixed in 3.4
https://issues.apache.org/jira/browse/ZOOKEEPER-335
A newly elected leader currently doesn't log the new leader transaction to
its database
In your case, the
