Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82594

Verify IndexBuildCoordinator behavior during config change.

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 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)

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: