Re: Consumer offset is getting reset back to some old value automatically

Michael, as I understand it's "risky" if another (2nd) node would fail, in this case your zookeeper will be not operational, right? But if no other issues it shouldn't affect operations. On Wed, Jun 25, 2014 at 2:08 AM, Michal Michalski wrote: > My understanding is that "bringing down 1 node our

Re: Consumer offset is getting reset back to some old value automatically

My understanding is that "bringing down 1 node our of a 3 node zookeeper cluster is risky, since any subsequent leader election *might* not reach a quorum"and "It is less likely but still risky to some extent" - *"it might not reach a quorum"*, because you need both of the remaining nodes to be up

Re: Consumer offset is getting reset back to some old value automatically

Neha, thanks for the answer, I want to understand what is the case when: >>Also, bringing down 1 node our of a 3 node zookeeper cluster is risky, since any subsequent leader election might not reach a quorum I was thinking zookeeper guarantees quorum if only 1 node out of 3 fails? Thanks. On Tue

Re: Consumer offset is getting reset back to some old value automatically

See the explanation from the zookeeper folks here - " Because Zookeeper requires a majority, it is best to use an odd number of machines. For example, with four machines ZooKeeper can only handle the failure of a single machine; if two

Re: Consumer offset is getting reset back to some old value automatically

Sorry, i meant 5 nodes in previous question. On Tue, Jun 24, 2014 at 12:36 PM, Kane Kane wrote: > Hello Neha, > >>>ZK cluster of 3 nodes will tolerate the loss of 1 node, but if there is a > subsequent leader election for any reason, there is a chance that the > cluster does not reach a quorum. I

Re: Consumer offset is getting reset back to some old value automatically

Hello Neha, >>ZK cluster of 3 nodes will tolerate the loss of 1 node, but if there is a subsequent leader election for any reason, there is a chance that the cluster does not reach a quorum. It is less likely but still risky to some extent. Does it mean if you have to tolerate 1 node loss without

Re: Consumer offset is getting reset back to some old value automatically

Can you elaborate your notion of "smooth"? I thought if you have replication factor=3 in this case, you should be able to tolerate loss of a node? Yes, you should be able to tolerate the loss of a node but if controlled shutdown is not enabled, the delay between loss of the old leader and election

Re: Consumer offset is getting reset back to some old value automatically

Yes kane i have the replication factor configured as 3 On Tue, Jun 24, 2014 at 2:42 AM, Kane Kane wrote: > Hello Neha, can you explain your statements: > >>Bringing one node down in a cluster will go smoothly only if your > replication factor is 1 and you enabled controlled shutdown on the brok

Re: Consumer offset is getting reset back to some old value automatically

Hello Neha, can you explain your statements: >>Bringing one node down in a cluster will go smoothly only if your replication factor is 1 and you enabled controlled shutdown on the brokers. Can you elaborate your notion of "smooth"? I thought if you have replication factor=3 in this case, you shoul

Re: Consumer offset is getting reset back to some old value automatically

Bringing one node down in a cluster will go smoothly only if your replication factor is 1 and you enabled controlled shutdown on the brokers. Also, bringing down 1 node our of a 3 node zookeeper cluster is risky, since any subsequent leader election might not reach a quorum. Having said that, a par

Re: Consumer offset is getting reset back to some old value automatically

What are your consumer config values? On Mon, Jun 23, 2014 at 12:28 AM, Hemath Kumar wrote: > We have a 3 node cluster ( 3 kafka + 3 ZK nodes ) . Recently we came across > a strange issue where we wanted to bring one of the node down from cluster > ( 1 kafka + 1 zookeeper) for doing a maintenan