There is no error in controller.log and no log in state-change.log
On Wed, Jun 11, 2014 at 11:03 PM, Jun Rao wrote:
> It sounds like broker 5 didn't get the needed message from the controller.
> Was there any error in the controller and state-change log when the above
> error started?
>
> Thank
It sounds like broker 5 didn't get the needed message from the controller.
Was there any error in the controller and state-change log when the above
error started?
Thanks,
Jun
On Tue, Jun 10, 2014 at 10:00 PM, Bongyeon Kim
wrote:
> No, broker 5 is alive with log.
>
>
> [2014-06-11 13:59:45,17
No, broker 5 is alive with log.
[2014-06-11 13:59:45,170] ERROR Conditional update of path
/brokers/topics/topicTRACE/partitions/0/state with data
{"controller_epoch":1,"leader":5,"version":1,"leader_epoch":0,"isr":[5]} and
expected version 2 failed due to
org.apache.zookeeper.KeeperException
The info from kafka-topics is the correct one. Is broker 5 dead? It seems
that you can issue metadata request to it.
Thanks,
Jun
On Tue, Jun 10, 2014 at 8:26 PM, Bongyeon Kim
wrote:
> With some WARN log, Yes, it is.
>
> and I found interesting things separately before I mentioned.
> I have an
With some WARN log, Yes, it is.
and I found interesting things separately before I mentioned.
I have another clusters. I run 2 brokers on 1 machine for test. and I see same
problem before I mentioned, but I can’t see any error log on controller.log.
At this time, when I list topics with kafka-t
Ok. Was this host (broker id:1,host:c-ccp-tk1-a58,port:9091) up when the
controller had SocketTimeoutException?
Thanks,
Jun
On Mon, Jun 9, 2014 at 10:11 PM, Bongyeon Kim
wrote:
> No, I can see any ZK session expiration log.
>
> What I have to do to prevent this? Increasing '
> zookeeper.sessi
No, I can see any ZK session expiration log.
What I have to do to prevent this? Increasing 'zookeeper.session.timeout.ms'
can help?
On Tue, Jun 10, 2014 at 12:58 PM, Jun Rao wrote:
> This is probably related to kafka-1382. The root cause is likely ZK session
> expiration in the broker. Did you
This is probably related to kafka-1382. The root cause is likely ZK session
expiration in the broker. Did you see any?
Thanks,
Jun
On Mon, Jun 9, 2014 at 8:11 PM, Bongyeon Kim wrote:
> Hi, team.
>
> I’m using 0.8.1.
> I found some strange log repeatedly on server.log in one of my brokers and
