This was a brand new cluster, so 0 topics. Every broker had the same issue and it was all communication with itself. In any case - i deployed a later cut and it started working.
Cheers, Damian On 18 November 2015 at 02:15, Jun Rao <j...@confluent.io> wrote: > There is inter-broker communication. It seems that the broker got a > request more than the default allowed size (~10MB). How many > topic/partitions do you have on this cluster? Do you have clients running > on the broker host? > > Thanks, > > Jun > > > On Tue, Nov 17, 2015 at 4:10 AM, Damian Guy <damian....@gmail.com> wrote: > >> I would think not.... >> I'm bringing up a new 0.9 cluster and i'm getting the below Exception (and >> the same thing on all nodes) - the IP address is the IP for the host the >> broker is running on. I think DNS is a bit stuffed on these machines and >> maybe that is the cause, but... any ideas? >> >> [2015-11-17 04:01:30,248] WARN Unexpected error from /10.137.231.233; >> closing connection (org.apache.kafka.common.network.Selector) >> org.apache.kafka.common.network.InvalidReceiveException: Invalid receive >> (size = 1195725856 larger than 104857600) >> at >> >> org.apache.kafka.common.network.NetworkReceive.readFromReadableChannel(NetworkReceive.java:91) >> at >> >> org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:71) >> at >> >> org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:160) >> at >> org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:141) >> at >> org.apache.kafka.common.network.Selector.poll(Selector.java:286) >> at kafka.network.Processor.run(SocketServer.scala:413) >> at java.lang.Thread.run(Thread.java:745) >> > >
