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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v4.2, v4.0, v3.6
    • Repl 2019-10-21, Repl 2019-11-04
    • 19

    Description

      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.

      Attachments

        Activity

          People

            ali.mir@mongodb.com Ali Mir
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: