Hello Alex, Error 1,3 and 4 can be transient and expected if on broker startup/bouncing/shutdown, error 2 indicates the request type is incorrect: currently we only have up to type 10, which consumer client do you use to consume data?
I am not sure about the ZK error, but it seems indicating the host/port is not reachable. Guozhang On Wed, Mar 19, 2014 at 12:36 PM, alex kamil <alex.ka...@gmail.com> wrote: > we're getting hundreds of these errs with kafka 0.8 and topics become > unavailable after running for a few days, any ideas how to proceed? > > 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 <http://10.1.64.14:3888/> > > java.net.ConnectException: Connection refused > -- -- Guozhang
