CollectionCloner must not set _clientConnection without holding _mutex

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.6
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-11-19
    • 56
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The CollectionCloner sets _clientConnection without holding _mutex. This causes _cancelRemainingWork_inlock() to be able to read bad state. _clientConnection must only be set while holding _mutex. It is expected that _clientConnection is always set when _queryState is kRunning.

            Assignee:
            Tess Avitabile (Inactive)
            Reporter:
            Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: