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

Report the offending oplog entries if a batch contains non-increasing transaction numbers

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.9, 4.0.4, 4.1.5
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Sharding 2018-10-22, Sharding 2018-11-05
    • Case:

      Description

      If this invariant trips, currently it is impossible to figure out exactly what was the state of the oplog batch on the secondary node without getting the entire oplog and scanning through it. This is problematic from supportability point of view since it requires customers to upload their entire oplog, which could be quite large.

      Instead, we should include as much information as possible in the mongodb log before crashing the server to help us diagnose this invariant.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: