Force on This。
宋鑫/NemoVisky
i will try to reproduce this problem later this week.
Bouncing the broker fixed the issue but the issue surfaced again after a
period of time. A little more context about this is that the cluster was
deployed to VMs and I discovered that the issue appeared whenever CPU wait
time was extremely
Can you try bouncing that broker?
Thanks,
Mayuresh
On Thu, May 14, 2015 at 3:43 AM, tao xiao xiaotao...@gmail.com wrote:
Yes, it does exist in ZK and the node that had the
NotLeaderForPartitionException
is the leader of the topic
On Thu, May 14, 2015 at 6:12 AM, Jiangjie Qin
Yes, it does exist in ZK and the node that had the
NotLeaderForPartitionException
is the leader of the topic
On Thu, May 14, 2015 at 6:12 AM, Jiangjie Qin j...@linkedin.com.invalid
wrote:
Does this topic exist in Zookeeper?
On 5/12/15, 11:35 PM, tao xiao xiaotao...@gmail.com wrote:
Hi,
Does this topic exist in Zookeeper?
On 5/12/15, 11:35 PM, tao xiao xiaotao...@gmail.com wrote:
Hi,
Any updates on this issue? I keep seeing this issue happening over and
over
again
On Thu, May 7, 2015 at 7:28 PM, tao xiao xiaotao...@gmail.com wrote:
Hi team,
I have a 12 nodes cluster that
Hi,
Any updates on this issue? I keep seeing this issue happening over and over
again
On Thu, May 7, 2015 at 7:28 PM, tao xiao xiaotao...@gmail.com wrote:
Hi team,
I have a 12 nodes cluster that has 800 topics and each of which has only 1
partition. I observed that one of the node keeps
Hi team,
I have a 12 nodes cluster that has 800 topics and each of which has only 1
partition. I observed that one of the node keeps generating
NotLeaderForPartitionException that causes the node to be unresponsive to
all requests. Below is the exception
[2015-05-07 04:16:01,014] ERROR
