This was an issue with that consumer group in __consumer_offsets adn these were the steps we did to fix this issue   On a single broker run the below    1) find /kafka/data -name "*.log" | grep -i consumer | awk '{a=$1;b="kafka-run-class kafka.tools.DumpLogSegments --deep-iteration --print-data-log -files "a; print b}'   Now run each and every command on xxxx broker to see which log file has consumer group "prod-abc-events"    2) kafka-run-class kafka.tools.DumpLogSegments --deep-iteration --print-data-log -files  /kafka/data/sdc/__consumer_offsets-24/00000000000000000000.log  | grep -i 'prod-abc-events   Do steps above on all the brokers and make a list of all the files that have 'prod-abc-events' . In our instance we found 3 files that refrenced this group "prod-abc-events'    broker1: /kafka/data/sda/__consumer_offsets-24/00000000000000000000.log   broker2: /kafka/data/sdc/__consumer_offsets-24/00000000000000000000.log   broker3: /kafka/data/sdc/__consumer_offsets-24/00000000000000000000.log   We noticed that the .log file on broker1 was different in size and content from the remaining two.    We backed up the file from broker1 and then replaced it with the one from broker2 . and that has resolved this issue.    Most likely this happened to us when we ran kafka-reassign-partitions and drives reached 99% and then something broke in _consumer_offsets.  ... View more

Thank a lot!! this removed the error from the logs. 🙂 ... View more

Hi Rekon   As gezapeti suggests the patch is contained by CDH5.7.0+   If you are interested, you can also look it up at Cloudera's Oozie repository, https://github.com/cloudera/oozie . Here, switch to branch 'cdh5-4.1.0_5.7.0' and click commits. You can find the patch in commit  commit 830171c6514aad2e20ad6d0bf629a2cc6ba30b6c: https://github.com/cloudera/oozie/commit/830171c6514aad2e20ad6d0bf629a2cc6ba30b6c ... View more