[
https://issues.apache.org/jira/browse/KAFKA-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273077#comment-14273077
]
Henri Pihkala commented on KAFKA-1855:
--------------------------------------
Yes - a single node cluster, running on CentOS Linux 64-bit.
I was basically creating topics in small bursts, say 3-10 topics quickly one
after another. I can't say if this pattern was important in producing the bug
or not. I was creating topics by sending topic metadata requests using the Java
API and having auto.create.topics.enable=true.
Sometimes all the topics would be created perfectly fine, and sometimes a topic
or two would fail as described.
Let me know if I can provide any further information.
> Topic unusable after unsuccessful UpdateMetadataRequest
> -------------------------------------------------------
>
> Key: KAFKA-1855
> URL: https://issues.apache.org/jira/browse/KAFKA-1855
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Affects Versions: 0.8.2
> Reporter: Henri Pihkala
> Fix For: 0.8.2
>
>
> Sometimes, seemingly randomly, topic creation/initialization might fail with
> the following lines in controller.log. Other logs show no errors. When this
> happens, the topic is unusable (gives UnknownTopicOrPartition for all
> requests).
> For me this happens 5-10% of the time. Feels like it's more likely to happen
> if there is time between topic creations. Observed on 0.8.2-beta, have not
> tried previous versions.
> [2015-01-09 16:15:27,153] WARN [Controller-0-to-broker-0-send-thread],
> Controller 0 fails to send a request to broker
> id:0,host:192.168.10.21,port:9092 (kafka.controller.RequestSendThread)
> java.io.EOFException: Received -1 when reading from channel, socket has
> likely been closed.
> at kafka.utils.Utils$.read(Utils.scala:381)
> at
> kafka.network.BoundedByteBufferReceive.readFrom(BoundedByteBufferReceive.scala:54)
> at kafka.network.Receive$class.readCompletely(Transmission.scala:56)
> at
> kafka.network.BoundedByteBufferReceive.readCompletely(BoundedByteBufferReceive.scala:29)
> at kafka.network.BlockingChannel.receive(BlockingChannel.scala:108)
> at
> kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:146)
> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:60)
> [2015-01-09 16:15:27,156] ERROR [Controller-0-to-broker-0-send-thread],
> Controller 0 epoch 6 failed to send request
> Name:UpdateMetadataRequest;Version:0;Controller:0;ControllerEpoch:6;CorrelationId:48;ClientId:id_0-host_192.168.10.21-port_9092;AliveBrokers:id:0,host:192.168.10.21,port:9092;PartitionState:[40963064-cdd2-4cd1-937a-9827d3ab77ad,0]
> ->
> (LeaderAndIsrInfo:(Leader:0,ISR:0,LeaderEpoch:0,ControllerEpoch:6),ReplicationFactor:1),AllReplicas:0)
> to broker id:0,host:192.168.10.21,port:9092. Reconnecting to broker.
> (kafka.controller.RequestSendThread)
> java.nio.channels.ClosedChannelException
> at kafka.network.BlockingChannel.send(BlockingChannel.scala:97)
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
