By default opening a checkpoint cursor on a table will default to use the history store corresponding to that table. To refer to the proper history required for the table, both the table and the history store are to be from the same checkpoint for data consistency.
To avoid returning inconsistent data, during the opening of the checkpoint cursor, we loop until we find both the table and history store are from the same checkpoint.
WiredTiger doesn't allow checkpointing individual tables separately other than from the system-wide checkpoint except when the table is opened for the bulk cursor operation. Performing individual table checkpoints leads to table and history store mismatch. In these scenarios, opening a checkpoint cursor on that table waits indefinitely until it finds a proper table and history store to use.
- causes
-
SERVER-73599 Investigate (for WT) implications of opening a checkpoint cursor returns an error in MongoDB
-
- Closed
-
-
WT-10721 failed: race-condition-stress-sanitizer-test-3 on ubuntu2004-stress-tests [wiredtiger @ 5a2abd1c]
-
- Closed
-
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Open
-