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

after shard merge ops in change collection have no coresponding entry in oplog

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • QE 2023-02-20, QE 2023-03-06, QE 2023-03-20, QE 2023-04-03, QE 2023-04-17
    • 5

      this causes an issue when resuming and reading a large transaction because this function will search for the constituent applyOps entries of the large transaction in the oplog, but if the transaction happened before or during the shard merge, the entries will only be in the change collection.

            Assignee:
            mickey.winters@mongodb.com Mickey Winters
            Reporter:
            mickey.winters@mongodb.com Mickey Winters
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: