kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jun MA <mj.saber1...@gmail.com>
Subject Re: Elegant way to failover controller
Date Wed, 05 Apr 2017 16:20:20 GMT
Hi Todd,

Thanks for your reply. We are seeing issue that for some topic, the ISR is keep churning,
meaning that it will continuously shrink/expand ISR every about 10s. It doesn’t look like
the follower cannot catch up with the leader because those topics are inactivate. There is
one time that we failover the controller to a broker that has no partitions live on there,
and the problem is gone. So I’m wondering if ISR churning is because of controller has too
many pressure and cannot correctly coordinate with other brokers?
Another question: should we delete inactive topics or not, is that gonna cause trouble?

> On Apr 5, 2017, at 9:12 AM, Todd Palino <tpalino@gmail.com> wrote:
> You can force the controller to move, but you can’t control where it goes.
> To force the controller to move to another broker, delete the “/controller”
> znode in Zookeeper for the cluster. This will cause the current controller
> to resign and a new one to be elected, but it’s random as to what broker
> that will be.
> A better question here is why do you want to move the controller?
> -Todd
> On Wed, Apr 5, 2017 at 9:09 AM, Jun MA <mj.saber1990@gmail.com> wrote:
>> Hi,
>> We are running kafka and I’m looking for a elegant way to failover
>> controller to other brokers. Right now I have to restart the broker to
>> failover it to other brokers. Is there a way to failover controller to a
>> specific broker? Is there a way to failover it without restart the broker?
>> Thanks,
>> Jun
> -- 
> *Todd Palino*
> Senior Staff Engineer, Site Reliability
> Data Infrastructure Streaming
> linkedin.com/in/toddpalino

View raw message