Hi,
We're attempting to build a multi-site cluster:
1. web-tier and application tier is active in all sites
2. only one database is active at a time- normally in the designated
primary site
We want to use 3 sites to maintain a quorum. So, if the Primary site loses
sight of both of the
What you describe is relatively reasonable, even though Zookeeper is not
normally distributed across multiple data centers with all members getting
full votes. If you account for the limited throughput that this will impose
on your applications that use ZK, then I think that this can work well.
I take your point about reliability, but I have no option other than finding
a multi-site solution.
Unfortunately, in my experience sites are much less reliable than individual
machines, and so in a way coping with site failure is more important than
individual machine failure. I imagine that
Hi,
Is there any documentation describing the network requirements for running
Zookeeper ?
Our network admin has baffled me with all the reasons that multicast might
not work in our environment, and then I realised that I do not know what
network support Zookeeper requires.
regards,
Martin
Your network admin is correct. Multicast often doesn't work.
ZK does not use multicast at the network level. Where events or
notifications must go to many places (that SOUNDS like multicast, I know) it
uses very standard TCP connections.
For almost any known modern network, ZK should be just
That's good news.
Thanks again Ted.
regards,
Martin
On 6 March 2010 23:03, Ted Dunning ted.dunn...@gmail.com wrote:
Your network admin is correct. Multicast often doesn't work.
ZK does not use multicast at the network level. Where events or
notifications must go to many places (that
