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

OplogApplier batching logic erroneously reads oplog document size after std::moving.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0-rc5, 4.1.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-06-18
    • 15

      After moving the oplog entry object, it is accessed to determine the object size. After the move, my machine, says the size of the entry is 5 bytes. This messes up the byte size limit in the batching logic.

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: