-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-03-09
As part of this change the ReadThroughCache should be made to perform the loading asynchronously, on a separate thread rather than doing it inline on the thread of the caller to acquire.
The asynchronous implementation should add the following methods to the API:
- Future<ValueHandle> acquireAsync(const Key& key)
- ValueHandle acquire(OperationContext* opCtx, const Key& key)
If an invalidate is called for a key, which is being concurrently loaded, it is acceptable to interrupt the loading of the key if it is currently in progress, but the acquire should not fail.
- is depended on by
-
SERVER-45798 Infrastructure for Caching OCSP responses for the Client
- Closed
-
SERVER-46154 Make ReadThroughCache be driven by a vector clock
- Closed
- is duplicated by
-
SERVER-46442 Decouple AuthorizationManager update lock and long-running LDAP queries
- Closed
- is related to
-
SERVER-45215 Reads from default RWC cache shouldn't reuse user's read concern
- Closed
- related to
-
SERVER-46442 Decouple AuthorizationManager update lock and long-running LDAP queries
- Closed