Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Storage - Ra 2022-01-24
-
2
Description
There are several places in mongodb where set_timestamp is called with the commit_timestamp config. This is deprecated and they should be changed to durable_timestamp.
auto commitTSConfigString = "commit_timestamp={:x}"_format(truncTs.asULL());
|
invariantWTOK(conn->set_timestamp(conn, commitTSConfigString.c_str()));
|
auto oldestTSConfigString =
|
"force=true,oldest_timestamp={0:x},commit_timestamp={0:x}"_format(
|
newOldestTimestamp.asULL());
|
invariantWTOK(_conn->set_timestamp(_conn, oldestTSConfigString.c_str()));
|
if (force) {
|
stableTSConfigString =
|
"force=true,oldest_timestamp={0:x},commit_timestamp={0:x},stable_timestamp={0:x}"_format(
|
ts);
|
stdx::lock_guard<Latch> lk(_highestDurableTimestampMutex);
|
_highestSeenDurableTimestamp = ts;
|
} else {
|
stableTSConfigString = "stable_timestamp={:x}"_format(ts);
|
}
|
invariantWTOK(_conn->set_timestamp(_conn, stableTSConfigString.c_str()));
|
Attachments
Issue Links
- is depended on by
-
WT-8583 Remove commit_timestamp config from set_timestamp
-
- Closed
-
- is documented by
-
DOCS-15035 Investigate changes in SERVER-62383: Use durable_timestamp instead of commit_timestamp for set_timestamp
-
- Closed
-