The default replication factor is 1, so even if you have one broker
failure, you can run into a situation with no leader for some partitions.
You probably want to use a higher replication factor.
On Thu, Oct 31, 2013 at 12:07 PM, Jiang Jacky <[EMAIL PROTECTED]> wrote:
> Hi, Neha
> Thanks for replying, I am currently using the 0.8 version.
> I did not set any replication factor, it keeps the default from package.
> When I check the leader for that topic, it is none.
> It is weird, There is no problem for any other topics except that topic
> that I am using.
> For now, I cannot produce the bug, but it is produced in random time, can
> you tell me what setting shall I set to prevent from this?
> 2013/10/29 Neha Narkhede <[EMAIL PROTECTED]>
> > What is the replication factor and have you checked if there are leader
> > elections around the time you see the NoAvailableLeader exception? It is
> > important to figure out the root cause of NoAvailableLeader, but it is
> > transient and should fix itself. Are you using 0.8 HEAD ?
> > On Tue, Oct 29, 2013 at 5:57 PM, Jiang Jacky <[EMAIL PROTECTED]>
> > > Hi, Everyone
> > > For now, I have a kafka cluster, and there is only 1 partition in each
> > > node. i just also produce lots of messages to 1 topic only.
> > > Then, I have a problem, I used it for a while, the topic is crashed,
> > > error message is "NoAvailableLeader", but it is good for other topics
> > that
> > > I do not often use. So I have to cleanup the zookeeper cache, and
> > > it again, then that topic comes back normal.
> > > Can someone tell me how to fix that? I don't want to clean the
> > > sometimes in order to make the topic available. It seems not stable.
> > > Thanks
> > >