One of our consumers keeps getting an invalid message size exception. I'm
pretty sure that we don't have a message size this big (1.7G). We have two
other consumer groups consuming messages from the same Kafka instance
happily over the last few days.

Since we keep the logs around for a fixed interval and this consumer group
has fallen pretty far behind, is it possible that somehow log truncation is
causing this? We are on kafka 0.6 BTW.

At this point, I'm inclined to wipe out the "/consumers/<group>/offsets"
node in zookeeper to get this system going again. Would that be the
preferred way of getting out of this bad state?

Let me know if there is any other trouble shooting/diagnostics I can run on
 the system before I reboot!


[$DATE] ERROR k.c.FetcherRunnable [] - error in FetcherRunnable
kafka.common.InvalidMessageSizeException: invalid message size:1852339316
only received bytes:307196 at 0 possible causes (1) a single message larger
than the fetch size; (2) log corruption
at kafka.utils.IteratorTemplate.maybeComputeNext(IteratorTemplate.scala:58)
at kafka.utils.IteratorTemplate.hasNext(IteratorTemplate.scala:50)
at kafka.consumer.PartitionTopicInfo.enqueue(PartitionTopicInfo.scala:70)
at kafka.con...

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB