I am sorry Neha, so late to reply you. I will try that and let you know
anyway.
Thanks Neha,
2013/10/31 Neha Narkhede
> 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 h
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.
Thanks,
Neha
On Thu, Oct 31, 2013 at 12:07 PM, Jiang Jacky wrote:
> Hi, Neha
> Thanks for replying
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
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
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, the
error message is "NoAvailableLeader", but it is good for other topics that
I do no
