-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
I've noticed that running compact can cause an update to be propagated to the turtle file. This isn't correct. The compact is doing checkpoints of an explicit target, and we only expect the turtle file to be updated for full checkpoints.
I encountered this issue due to a recovery problem. Recovery was getting a starting LSN from the turtle file that corresponded to a file_sync log record, instead of a checkpoint log record. That LSN is being written into the turtle file when compact is run for a single btree.
- is depended on by
-
SERVER-19532 WiredTiger changes for MongoDB 3.1.7
- Closed
-
SERVER-19744 WiredTiger changes for MongoDB 3.0.6
- Closed
- related to
-
SERVER-19274 DB fails to recover after system crash, with "No such file or directory"
- Closed
-
WT-1581 Partial checkpoints may cause recovery failures
- Closed