Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.9.0
Description
When the index is corrupt all bets are off and we need to replay the journal to rebuild the index. We do this automatically on a failure to load the index. When the index loads and is still corrupt, we can resume and messages are unavailable.
Adding some sanity checking to the index, when checkForCorruptJournalFiles is enabled (paranoid mode) will allow us to detect corruption and force an auto recreation.