What this means is that the CRC that was stored with the data no longer
matches. There could be two reasons for this:
1. We have some rare bug in the CRC calculation or check logic or are
otherwise corrupting data in flight
2. You have disk or network corruption which changed the bits.
To diagnose
Jay, we have observed CRC corruption too occasionally. I reported in an
thread and asked how should we handle some error conditions from old
high-level consumer.
On Mon, Feb 9, 2015 at 11:36 PM, Bhavesh Mistry
wrote:
> Hi Jay,
>
> 1) Sorry to get back to you so late. It is CRC check error on an
Hi Jay,
1) Sorry to get back to you so late. It is CRC check error on any consumer
thread regardless of the server. What happens is I have to catch this
exception is skip the message now. There is no option to re-fetch this
message. Is there any way to add behavior in Java consumer to re-fet
Hey Bhavesh,
This seems like a serious issue and not one anyone else has reported. I
don't know what you mean by corrupt message, are you saying the CRC check
fails? If so, that check is done both by the broker (prior to appending to
the log) and the consumer so that implies either a bug in the br
Hi Jay,
One of the pain point of existing consumer code is CORRUPT_MESSAGE
occasionally. Right now, it is hard to pin-point the problem of
CORRUPT_MESSAGE especially when this happen on Mirror Maker side. Is there
any proposal to auto skip corrupted message and have reporting visibility
of CRC err
