You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ben Edwards (JIRA)" <ji...@apache.org> on 2015/05/15 18:11:00 UTC
[jira] [Updated] (KAFKA-2197) Controller not able to update state
for broker on the same machine
[ https://issues.apache.org/jira/browse/KAFKA-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben Edwards updated KAFKA-2197:
-------------------------------
Description:
I am using kafka on docker. When I try to create a topic the controller seems to get stuck and the topic is never usable for consumers or producers.
{noformat}
[2015-05-15 15:51:10,201] WARN [Controller-9092-to-broker-9092-send-thread], Controller 9092 epoch 1 fails to send request Name:LeaderAndIsrRequest;Version:0;Controller:9092;ControllerEpoch:1;CorrelationId:7;ClientId:id_9092-host_null-port_9092;Leaders:id:9092,host:kafka,port:9092;PartitionState:(lol,0) -> (LeaderAndIsrInfo:(Leader:9092,ISR:9092,LeaderEpoch:0,ControllerEpoch:1),ReplicationFactor:1),AllReplicas:9092) to broker id:9092,host:kafka,port:9092. Reconnecting to broker. (kafka.controller.RequestSendThread)
java.nio.channels.ClosedChannelException
at kafka.network.BlockingChannel.send(BlockingChannel.scala:100)
at kafka.controller.RequestSendThread.liftedTree1$1(ControllerChannelManager.scala:132)
at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:131)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:60)
{noformat}
Repro steps:
run docker-compose up with the attached docker-compose yaml file.
enter the kafka container (get the name with {{docker ps}}, {{docker exec -it <<name>> bash}} to enter).
run the following
{noformat}
cd /opt/kafka_2.10-0.8.2.1/
./bin/kafka-topics.sh --list --zookeeper zk:2181
./bin/kafka-topics.sh --create --zookeeper zk:2181 --topic lol --replicatior-factor 1 --partitions 1
./bin/kafka-topics.sh --create --zookeeper zk:2181 --topic testing --replication-factor 1 --partitions 1
./bin/kafka-topics.sh --list --zookeeper zk:2181
tail -f logs/controller.log
{noformat}
This should allow you to observe the controller being upset. The zookeeper instance is definitely reachable, the hostnames are correct as far as I can tell. I am kind of at a loss as to what is happening.
was:
I am using kafka on docker. When I try to create a topic the controller seems to get stuck and the topic is never usable for consumers or producers.
{noformat}
[2015-05-15 15:51:10,201] WARN [Controller-9092-to-broker-9092-send-thread], Controller 9092 epoch 1 fails to send request Name:LeaderAndIsrRequest;Version:0;Controller:9092;ControllerEpoch:1;CorrelationId:7;ClientId:id_9092-host_null-port_9092;Leaders:id:9092,host:kafka,port:9092;PartitionState:(lol,0) -> (LeaderAndIsrInfo:(Leader:9092,ISR:9092,LeaderEpoch:0,ControllerEpoch:1),ReplicationFactor:1),AllReplicas:9092) to broker id:9092,host:kafka,port:9092. Reconnecting to broker. (kafka.controller.RequestSendThread)
java.nio.channels.ClosedChannelException
at kafka.network.BlockingChannel.send(BlockingChannel.scala:100)
at kafka.controller.RequestSendThread.liftedTree1$1(ControllerChannelManager.scala:132)
at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:131)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:60)
{noformat}
Repro steps:
run docker-compose up with the attached docker-compose yaml file.
enter the kafka container (get the name with {{docker ps}}, {{docker exec -it <<name>> bash}} to enter).
run the following
{monospace}
cd /opt/kafka_2.10-0.8.2.1/
./bin/kafka-topics.sh --list --zookeeper zk:2181
./bin/kafka-topics.sh --create --zookeeper zk:2181 --topic lol --replicatior-factor 1 --partitions 1
./bin/kafka-topics.sh --create --zookeeper zk:2181 --topic testing --replication-factor 1 --partitions 1
./bin/kafka-topics.sh --list --zookeeper zk:2181
tail -f logs/controller.log
{monospace}
This should allow you to observe the controller being upset. The zookeeper instance is definitely reachable, the hostnames are correct as far as I can tell. I am kind of at a loss as to what is happening.
> Controller not able to update state for broker on the same machine
> ------------------------------------------------------------------
>
> Key: KAFKA-2197
> URL: https://issues.apache.org/jira/browse/KAFKA-2197
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Affects Versions: 0.8.2.1
> Environment: docker 1.5, 64 bit Linux (4.0.1-1).
> Reporter: Ben Edwards
> Assignee: Neha Narkhede
>
> I am using kafka on docker. When I try to create a topic the controller seems to get stuck and the topic is never usable for consumers or producers.
> {noformat}
> [2015-05-15 15:51:10,201] WARN [Controller-9092-to-broker-9092-send-thread], Controller 9092 epoch 1 fails to send request Name:LeaderAndIsrRequest;Version:0;Controller:9092;ControllerEpoch:1;CorrelationId:7;ClientId:id_9092-host_null-port_9092;Leaders:id:9092,host:kafka,port:9092;PartitionState:(lol,0) -> (LeaderAndIsrInfo:(Leader:9092,ISR:9092,LeaderEpoch:0,ControllerEpoch:1),ReplicationFactor:1),AllReplicas:9092) to broker id:9092,host:kafka,port:9092. Reconnecting to broker. (kafka.controller.RequestSendThread)
> java.nio.channels.ClosedChannelException
> at kafka.network.BlockingChannel.send(BlockingChannel.scala:100)
> at kafka.controller.RequestSendThread.liftedTree1$1(ControllerChannelManager.scala:132)
> at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:131)
> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:60)
> {noformat}
> Repro steps:
> run docker-compose up with the attached docker-compose yaml file.
> enter the kafka container (get the name with {{docker ps}}, {{docker exec -it <<name>> bash}} to enter).
> run the following
> {noformat}
> cd /opt/kafka_2.10-0.8.2.1/
> ./bin/kafka-topics.sh --list --zookeeper zk:2181
> ./bin/kafka-topics.sh --create --zookeeper zk:2181 --topic lol --replicatior-factor 1 --partitions 1
> ./bin/kafka-topics.sh --create --zookeeper zk:2181 --topic testing --replication-factor 1 --partitions 1
> ./bin/kafka-topics.sh --list --zookeeper zk:2181
> tail -f logs/controller.log
> {noformat}
> This should allow you to observe the controller being upset. The zookeeper instance is definitely reachable, the hostnames are correct as far as I can tell. I am kind of at a loss as to what is happening.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)