Just for sake of future forums readers, the solution to the "leader
flapping" problem I described was to increase the zookeeper session timeout
setting (zookeeper.session.timeout.ms). I believe we doubled it (15000ms to
3ms).
For the ReplicaFetcherThread and
https://issues.apache.org/jira/brow
Hi Jiangjie,
There's is nothing of note in the controller log. I've attached that log
along with the state change log in the following gist:
https://gist.github.com/banker/78b56a3a5246b25ace4c
This represents a 2-hour period on April 15th.
Since I've disabled the broker on question (on April 15t
It seems there are many different symptoms you see...
Maybe we can start from leader flapping issue. Any findings in controller
log?
Jiangjie (Becket) Qin
On 4/16/15, 12:09 PM, "Kyle Banker" wrote:
>Hi,
>
>I've run into a pretty serious production issue with Kafka 0.8.2, and I'm
>wondering w
Hi,
I've run into a pretty serious production issue with Kafka 0.8.2, and I'm
wondering what my options are.
ReplicaFetcherThread Error
I have a broker on a 9-node cluster that went down for a couple of hours.
When it came back up, it started spewing constant errors of the following
form:
INFO
