Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2024-01-22
-
2
Description
A lock is taken in VectorClock::isEnabled to check if VectorClock is enabled. It appears that VectorClock can only ever be disabled if a node becomes an arbiter and cannot be renabled. Since VectorClock::isEnabled is called several times in a request (gossipIn during request processing, gossipOut during reply processing and potentially over times (like getting legacy runtime constants)). This will help reduce contention on the VectorClock mutex and save time.
Attachments
Issue Links
- related to
-
SERVER-82647 Avoid getting current VectorClock in Variables::generateRuntimeConstants
-
- Closed
-