Reconfig cmd should wrap the no-op oplog write in writeConflictRetry block.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • v4.2, v4.0, v3.6
    • Repl 2019-10-21, Repl 2019-11-04
    • 19
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, reconfig cmd does not wrap the  no-op oplog write write in a writeConflictRetry block. It's always safe to wrap any writes to a record store in a writeConflictRetry block because writeConflict exception can be thrown in the mongodb layer even for some memory pressure/issues in WiredTiger.

            Assignee:
            Ali Mir
            Reporter:
            Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: