-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Execution Team 2023-11-27, Execution Team 2023-12-11
The IndexBuildCoordinator obtains the Replication Coordinator member configuration using replCoord->findConfigMemberByHostAndPort() in two places. Since the configuration could change before this call returns, it's not clear if this is conceptually a safe thing to do. We should verify that the IndexBuildCoordinator behaves correctly during configuration changes.
(There's currently an actual race, which will be fixed by SERVER-82259, but the issue of stale config data remains)
- is related to
-
SERVER-82259 replCoord->findConfigMemberByHostAndPort is inherently racy
- Closed
-
SERVER-83857 Allow index builds to be resumable on non-voting nodes
- Closed