I opened this issue 3 weeks ago on the issue tracker: https://issues.apache.org/jira/browse/KAFKA-15467
Every time I lose power at one of these remote hosts, when the power comes back up and the broker restarts, I have several (not all) topics report offsets as missing back to mirrormaker2, resulting in a large amount of messages being re-synced. The odd part is if you go to the broker and ask again, it happily sends the ‘missing’ offset back. I could use some help trying to collect more information about this issue. I’ve been able to enable trace level logging for requests and I can line up the request that matches with an offset out of range when the MM2 consumer requests the offset, but I’m unable to ‘prove’ that the broker is responding with the offset out of range response. I can’t seem to figure out what trace level log option I need to enable to see this. Also, this seems like a pretty bad bug for Kafka to have, it is amazing to me no one has responded about. I can reproduce this consistently now on a test node by resetting power to the machine. Any help would be greatly appreciated, thank you! -Steve Jacobs
