okeeper cluster is risky,
> > since any subsequent leader election might not reach a quorum. Having
> said
> > that, a partition going offline shouldn't cause a consumer's offset to
> > reset to an old value. How did you find out what the consumer's offset
> was
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 maintenance . But the movement we
brought it to down on some of the topics ( only some partitions) consumers
of
e info to check the reasons kafka stopped working. For
> consumer offset checker tool, you need to specify the topic names,
> otherwise you will see "empty.head".
>
> Guozhang
>
>
> On Tue, May 27, 2014 at 9:53 PM, Hemath Kumar
> wrote:
>
> > This is t
, Guozhang Wang wrote:
> Hi,
>
> Could you print the full command line you used consumer offset checker
> tool?
>
> Guozhang
>
>
> On Tue, May 27, 2014 at 12:46 AM, Hemath Kumar
> wrote:
>
> > Every time when i reboot my machine kafka is not working. when i c
Every time when i reboot my machine kafka is not working. when i check the
consumeroffset tool i am getting this error. I am new to this i could not
figure out what could be the issues.
I am saving the logs in /data/zk and /data/kafka. And its running on single
node. Would appriciate if any one c
