In 0.7, one way to do this is to use a vip. All producers send data to the vip. To decommission a broker, you first take the broker out of vip so no new data will be produced to it. Then you let the consumer drain the data (you can use ConsumerOffsetChecker to check if all data has been consumed). Finally, you can shut down the broker.
This will be much easier in 0.8 because of replication.
On Sat, Jan 5, 2013 at 11:34 PM, Bae, Jae Hyeon <[EMAIL PROTECTED]> wrote:
In 0.8, we will provide a way for your to shutdown the broker in a controlled fashion. What that would include is moving all the leaders away from the broker so that it does not take any more produce requests. Once that is done, you can shutdown the broker normally. You don't have to wait until the consumers have pulled the data simply because they can consume from the new leader.
Thanks, Neha On Sun, Jan 6, 2013 at 8:52 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
OK, I will try after you release stable build of 0.8
Thank you Best, Jae
On Sun, Jan 6, 2013 at 10:36 AM, Neha Narkhede <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext