Investigate if we should take stronger locks during setFCV

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 8.2 Required
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we only briefly take/immediately release the global lock one time during setFCV (after the FCV is in the transitional FCV and before the FCV is in the final fully upgraded/downgraded state).

      Operations can interleave with this lock in complex ways (see comment for more details). We should investigate if taking stronger locks (for example, taking this global lock barrier twice (once before each oplog entry write), or maybe taking the global lock during the whole operation) would help make this less complex and allow operations to serialize better with setFCV at least in terms of the locking.

            Assignee:
            Unassigned
            Reporter:
            Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: