-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
-
Repl 2022-05-30, Repl 2022-06-13, Repl 2022-06-27
-
5
As seen in BF-25138, ThreadSanitizer reports a data race surrounding the usage of setCurrentCommittedSnapshotOpTime() in the ReplicationCoordinatorMock. The actual implementation of the replication coordinator holds a lock while doing similar updates.
- is caused by
-
SERVER-54394 Remove flag to avoid using snapshot read concern in ConfigServerCatalogCacheLoader on unit_tests
- Closed
-
SERVER-61772 Implement tenant access blocking for the split service
- Closed