Sent: Wednesday, August 21, 2013 8:36 PM
To: users@kafka.apache.org
Subject: Re: broker never comes back to ISR
Thanks for sending this across. One thing that is weird about the thread dump
is that the thread names are not included, so it is somewhat difficult to read.
But just from the stack trac
rg
Subject: Re: broker never comes back to ISR
Thanks for sending this across. One thing that is weird about the thread dump
is that the thread names are not included, so it is somewhat difficult to read.
But just from the stack traces, I don't see the ReplicaFetcherThreads alive.
Can you g
transport.tcp.TCPTransport$AcceptLoop.run() @bci=1, line=359
> (Interpreted frame)
> - java.lang.Thread.run() @bci=11, line=722 (Interpreted frame)
>
>
> Thread 5135: (state = BLOCKED)
>
>
> Thread 5134: (state = BLOCKED)
> - java.lang.Object.wait(long) @bci=0 (Interpreted frame)
> -
[]) @bci=4 (Interpreted frame)
Regards,
Libo
-Original Message-
From: Neha Narkhede [mailto:neha.narkh...@gmail.com]
Sent: Wednesday, August 21, 2013 11:53 AM
To: users@kafka.apache.org
Subject: RE: broker never comes back to ISR
Could you take a thread dump on that broker and send it acro
Could you take a thread dump on that broker and send it across? One of the
possibilities is the replica fetcher thread is somehow dead.
Thanks,
Neha
On Aug 21, 2013 8:00 AM, "Yu, Libo" wrote:
> I checked the log of normal restart. The replication manager should start
> to handle
> leader and isr
I checked the log of normal restart. The replication manager should start to
handle
leader and isr request after the server is up. What may stop it from doing that?
Is it because of missing mx4j-tools.jar?
Regards,
Libo
From: Yu, Libo [ICG-IT]
Sent: Wednesday, August 21, 2013 10:51 AM
To: 'user
