Is it so that only ensemble would be down but other functions would be up
and running like data-sync ... ?
Say, if a ZooKeeper server lost connection with the quorum. It will shutdown
all the services and try to join the quorum by starting internal election algo.
There is a special type of
Rakesh Garry,
Thanks for the information and details. From both of your responses I can see
that, more failures will cause drop of quorum automatically.
Is it so that only ensemble would be down but other functions would be up and
running like data-sync ... ? Sorry If this is very basic
Thank you Alex for the info.
Hi Srini, I think Observer would be fine for your case. Probably you can try it
out.
-Rakesh
On 13 Jul 2015 21:41, Alexander Shraer shra...@gmail.com wrote:
In 3.4 releases you can't connect an observer to a standalone zookeeper
server, but in 3.5.0
if you
Thanks to all of you guys. I will try it out.
By any chance does anyone know when would the final/stable version of 3.5.0 be
available. Because I can see it's in 3.5.0-alpha.
Thanks,
Srini
-Original Message-
From: Rakesh [mailto:rakeshr.apa...@gmail.com]
Sent: Tuesday, July 14, 2015
negative ids could break stuff, such as here:
https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumCnxManager.java#L321
On Mon, Jul 13, 2015 at 11:07 AM, Raúl Gutiérrez Segalés
r...@itevenworks.net wrote:
Hi,
On 13 July 2015 at 10:43,
Hi,
On 13 July 2015 at 10:43, Benjamin Anderson b...@banjiewen.net wrote:
Hi there - I've observed that the documentation[1] suggests that each
node's myid should be an integer in the range [1, 255]. Is that
limitation codified anywhere? A quick perusal of the source suggests
that myid is
Hi there - I've observed that the documentation[1] suggests that each
node's myid should be an integer in the range [1, 255]. Is that
limitation codified anywhere? A quick perusal of the source suggests
that myid is parsed in to a Long and passed around as such through the
codebase.
For context,
In 3.4 releases you can't connect an observer to a standalone zookeeper
server, but in 3.5.0
if you set standaloneEnabled=false your server will run in a distributed
mode even if its the only one and
you'll be able to have observers or reconfigure adding more servers later
if needed.
On Mon, Jul
Hi,
We know ZK demands odd number of servers to provide reliability.
My requirement on having zookeeper in my application is to know the
application status from all the clients(Max 100).
And today my application can support deployment 1+1(=2) to N+1(=100)
Given this I would like to go with 2 ZK
Hi,
I claim no ZK expertise but did have a similar scenario so I'll share my
conclusion and then the ZK experts can point out how wrong I am. :)
The odd number of servers requirement is because a ZK consensus can only be
formed by an *absolute* majority of nodes in the ensemble. With an even
Hi Srini,
ZooKeeper service will be available if 'quorum' number of servers are
running(simple majority voting factors).
I could see, one of the reason to get a majority vote is to avoid split-brain
problem. In a network failure we don't want the two parts of the system to
continue as usual.
11 matches
Mail list logo
