Re: Graceful termination of kafka broker after draining all the data consumed

2013-02-18 Thread 王国栋
Thanks Jun. I will check more info about 0.8 On Tue, Feb 19, 2013 at 12:51 AM, Jun Rao wrote: > In 0.7, it's not very easy to decommission a broker using ZK based > producers. It's possible to do that with a vip (then you can't do > partitioning). In 0.8 (probably 0.8.1), you can use a tool t

Re: Where is broker 'current offset' stored in ZooKeeper?

2013-02-18 Thread Chris Curtin
Thanks Jun. Looks like a couple of ways to do this based on how operations wants to manage things. Thanks, Chris On Mon, Feb 18, 2013 at 12:04 PM, Jun Rao wrote: > All zk paths in 0.8 are documented in > > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+data+structures+in+Zookeeper >

Re: Where is broker 'current offset' stored in ZooKeeper?

2013-02-18 Thread Jun Rao
All zk paths in 0.8 are documented in https://cwiki.apache.org/confluence/display/KAFKA/Kafka+data+structures+in+Zookeeper In 0.8, there is a jmx bean (ConsumerLag) in the consumer under kafka.server that monitors the lag of each partition in terms of messages. We also have a command line tool Con

Re: Graceful termination of kafka broker after draining all the data consumed

2013-02-18 Thread Jun Rao
In 0.7, it's not very easy to decommission a broker using ZK based producers. It's possible to do that with a vip (then you can't do partitioning). In 0.8 (probably 0.8.1), you can use a tool to move all partitions off a broker first and then decommission it. Thanks, Jun On Sun, Feb 17, 2013 at