[
https://issues.apache.org/jira/browse/KAFKA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941786#comment-13941786
]
Jun Rao commented on KAFKA-1314:
--------------------------------
When mytopic is unavailable? Are there any errors in the controller and the
state-change logs? Also, what's the output when you describe a topic?
> recurring errors
> ----------------
>
> Key: KAFKA-1314
> URL: https://issues.apache.org/jira/browse/KAFKA-1314
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: alex kamil
> Priority: Critical
>
> we're getting hundreds of these errs with kafka 0.8 and topics become
> unavailable after running for a few days
> kafka error 1 (had to recreate the topic as it became unavailable after a few
> days)
> [2014-03-18 16:34:56,403] ERROR [KafkaApi-3] Error while fetchingmetadata for
> partition [mytopic,0] (kafka.server.KafkaApis)
> kafka.common.LeaderNotAvailableException: Leader not available for partition
> [mytopic,0]
> kafka error 2
> [2014-03-17 12:23:27,536] ERROR Closing socket for /<kafka consumer ip
> address> because of error (kafka.network.Processor)
> kafka.common.KafkaException: Wrong request type 768
> kafka error 3
> ERROR Closing socket for /<kafka consumer ip address> because of error
> (kafka.network.Processor)
> java.io.IOException: Connection reset by peer
> kafka error 4
> ERROR Closing socket for /<kafka broker ip address> because of error
> (kafka.network.Processor)
> zookeeper error
> 2014-03-18 16:40:02,794 [myid:3] - WARN
> [QuorumPeer[myid=3]/0.0.0.0:2181:QuorumCnxManager@368] - Cannot open channel
> to 1 at election address /<kafka broker ip address>:3888
> java.net.ConnectException: Connection refused
--
This message was sent by Atlassian JIRA
(v6.2#6252)
