Will definitely take a thread dump! So, far its been running fine.
-Jacob
On Wed, Oct 15, 2014 at 8:40 PM, Jun Rao wrote:
> If you see the hanging again, it would be great if you can take a thread
> dump so that we know where it is hanging.
>
> Thanks,
>
> Jun
>
> On Tue, Oct 14, 2014 at 10:35
If you see the hanging again, it would be great if you can take a thread
dump so that we know where it is hanging.
Thanks,
Jun
On Tue, Oct 14, 2014 at 10:35 PM, Abraham Jacob
wrote:
> Hi Jun,
>
> Thanks for responding...
>
> I am using Kafka 2.9.2-0.8.1.1
>
> I looked through the controller lo
Hi Jun,
Thanks for responding...
I am using Kafka 2.9.2-0.8.1.1
I looked through the controller logs on a couple of nodes and did not find
any exceptions or error.
However in the state change log I see a bunch of the following exceptions -
[2014-10-13 14:39:12,475] TRACE Controller 3 epoch 116
Also, which version of Kafka are you using?
Thanks,
Jun
On Tue, Oct 14, 2014 at 5:31 PM, Jun Rao wrote:
> The following is a bit weird. It indicates no leader for partition 4,
> which is inconsistent with what describe-topic shows.
>
> 2014-10-13 19:02:32,611 WARN [main] kafka.producer.BrokerP
The following is a bit weird. It indicates no leader for partition 4, which
is inconsistent with what describe-topic shows.
2014-10-13 19:02:32,611 WARN [main] kafka.producer.BrokerPartitionInfo:
Error while fetching metadata partition 4 leader: nonereplicas: 3
(tr-pan-hclstr-13.amers1b.
Hi All,
I have a 8 node Kafka cluster (broker.id - 1..8). On this cluster I have a
topic "wordcount", which was 8 partitions with a replication factor of 3.
So a describe of topic wordcount
# bin/kafka-topics.sh --describe --zookeeper
tr-pan-hclstr-08.amers1b.ciscloud:2181/kafka/kafka-clstr-01 --
