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

Report writeConflicts in serverStatus on secondaries

    XMLWordPrintableJSON

Details

    • Replication
    • Fully Compatible
    • v7.0, v6.0, v5.0, v4.4
    • Repl 2023-07-24

    Description

      Primary records the number of writeConflicts in serverStatus by calling recordCurOpMetrics() in the write path, however secondaries never do that. It is helpful to show writeConflicts counter in serverStatus on secondaries since it can help identify issues during secondary oplog application. For example, we saw a problem on secondary that due to the transaction size exceeding cache threshold, the oplog application got stuck in the writeConflict retry loop. Not recording writeConflicts on secondaries made it hard to confirm the issue and we had to rely on other indirect evidences.

      Attachments

        Activity

          People

            wenbin.zhu@mongodb.com Wenbin Zhu
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: