-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
Fully Compatible
-
Storage NYC 2018-04-09, Storage NYC 2018-04-23, Storage NYC 2018-05-07, Storage NYC 2018-05-21, Storage NYC 2018-06-04
In 3.6, we permit reads back to the majority commit point (approximately: a little additional slack is currently built in). Attempts to read at an older point will fail.
For Global Point in Time Reads, a mongos will need to establish a common timestamp across all mongod nodes involved in a query. In order to do that, it would be helpful for each node to store some additional history.
WiredTiger could monitor when it is under cache pressure from storing history, and update the oldest_timestamp in response, with the goal of allowing reads older than the majority commit point where possible without impacting performance.
We should also consider whether to make the "comfort level" configurable, to maintain some history even on memory constrained nodes to increase the chance of finding a common point in time across a cluster.
- depends on
-
WT-3974 Add a measurement of cache pressure caused by storing history
-
- Closed
-
- is depended on by
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-35023 Add server parameter maxTransactionLockRequestTimeoutMillis test
-
- Closed
-
- is related to
-
WT-4101 Don't abort the eviction server during session verify when oldest_timestamp is held back
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-