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

replCoord->findConfigMemberByHostAndPort is inherently racy

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v7.2
    • Repl 2023-11-13, Repl 2023-11-27
    • 120

      In https://jira.mongodb.org/browse/SERVER-47828 we switched from returning a member configuration by copy to returning a pointer. Unfortunately that pointer is to data protected by the repl mutex and can change. We can't switch back to a copy (too slow, which was the original reason for the ticket) so we'll need to come up with another solution.

      It's possible there's a bigger issue, in that I'm not sure how the index build coordinator handles it when configurations change while it's running. We may need something like an external config lock.

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: