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
dle
> 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: 'users@kafka.apache.org'
&g
: 'users@kafka.apache.org'
Subject: broker never comes back to ISR
Hi team,
We have three kafka brokers in a production cluster. We use replication factor
3 for all topics.
We notice quite frequently one broker is not in isr. Sometimes after it is
restarted, it
will go back to isr. Some
Hi team,
We have three kafka brokers in a production cluster. We use replication factor
3 for all topics.
We notice quite frequently one broker is not in isr. Sometimes after it is
restarted, it
will go back to isr. Sometimes even after it is restarted, it will not go back
to isr.
In today's c
