@suiyuzeng That's right. The final reason is just as you analyzed, the message was damaged in commitlog, but the recovering process dose not detect it. In fact, not only the abnormal recovering, but also the normal recovering should check isSuccess, and truncate the log when isSuccess is false. Could you submit a PR for this issue? I could help to review and merge it.
[ Full content available at: https://github.com/apache/rocketmq/issues/467 ] This message was relayed via gitbox.apache.org for [email protected]
