-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2024-06-10, Repl 2024-11-11
Logical initial sync attempts to set the stable timestamp to 0 during setup. This is actually a no-op because we would return early here.
This shouldn't be a correctness issue, since we expect the stable timestamp to be null until initial sync completes successfully (even if it fails once and retries the initial sync), but we should make sure to properly use the WT API.
- is related to
-
SERVER-84706 Investigate if setting the oldest timestamp greater than the stable timestamp can be avoided
- Closed
-
SERVER-86659 Review WT_CONNECTION.set_timestamp calls
- Closed