Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
Edit log branch (HDFS-1073)
-
None
Description
In the 1073 branch, the NN is much more careful on startup to make sure it isn't missing any transactions, etc. For example, if
one of the log segments is missing, it will refuse to start up with a message like "Expected next log group would start at txid 502 but starts at txid 516". It would be nice to provide a last-ditch escape hatch, similar to InnoDB's force recovery modes to allow the operator to tell the NN to attempt to push past any such problems, with data loss expected.
Attachments
Issue Links
- relates to
-
HDFS-3004 Implement Recovery Mode
- Closed