Thanks Ted,
frankly speaking, your answer makes me nervous about upgrade Zookeeper
server. Hope the developers of Zookeeper thinking about it. I think
Zookeeper is very cool. But it isn't good enough for online systems if it
cannot be upgraded without losing existed data.
Thanks
On Sat, Jun 27
I don't think you should be very nervous at all.
There are two questions:
1) can 3.1.1 go to 3.2 with no down time. This is very likely, but a wiser
head than mine should have final say
2) can 3.1.1 go to 3.2 with < 1 minute of downtime. The is for sure.
Neither option involves data loss.
ZK
Thanks for the explanation, it sounds great.
It seems that I should study more on Zookeeper :-)
regards
On Mon, Jun 29, 2009 at 2:15 AM, Ted Dunning wrote:
> I don't think you should be very nervous at all.
>
> There are two questions:
>
> 1) can 3.1.1 go to 3.2 with no down time. This is ver
A related question. If I have run a Zookeeper service with many ephemeral
znodes on five servers, then I want to replace one of the servers by a new
one, and the new server has a new IP. How can I do the job without any loss
of data ?
Thanks
On Mon, Jun 29, 2009 at 9:24 AM, Qian Ye wrote:
> T
A rolling update works very well for that. You can also change the number
of nodes in the cluster.
To do this, you replace the config files on the surviving servers and on the
new server.
Then take down the one that is leaving the cluster and then one by one
restart the servers that will remain
