OplogFetcherMock must avoid calling join() from multiple threads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      join() may only be called on a given thread once; calling it multiple times or simultaneously results in a fatal error. The construction currently used (if joinable then join) is not synchronized and thus racy. Simply locking the current mutex around this call will not work because it will deadlock, but adding another mutex just for this might be fine.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Matthew Russotto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: