Feature #6290
Journaler: warn and shut down if we hit end of journal too early
Status:
Resolved
Priority:
High
Assignee:
-
Category:
Correctness/Safety
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:
Description
If a gap gets created in the journal, the Journaler shuts down replay but doesn't warn that it hit ENOENT unexpectedly early (or didn't find a LogEvent, or whatever). Often this happens at a point when the Journaler knows that there should be data available. In that case, the Journaler should print a warning and shut down the MDS (with an option to not do so, of course). This could prevent a lost journal object from eradicating all updates in the following objects.
History
#1 Updated by Greg Farnum almost 8 years ago
- Category changed from 47 to Correctness/Safety
#2 Updated by Greg Farnum over 7 years ago
- Status changed from New to Resolved
Looks like this got fixed in our Journaler refactor.