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

Investigate faster BSON stream reading in magic restore

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Replication

    Description

      After we get performance results from SERVER-83352, we should investigate if we can make the BSON stream reading of additional oplog entries faster. The default behavior is serially threading the stream, constructing an oplog entry, and writing it into the oplog collection.

      Some ideas include: can we split up reading the stream and writing the oplog entries into the oplog collection into multiple threads? Can we devise a smarter way of storing the additional oplog entries in S3 so we don't have to read the stream serially?

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            ali.mir@mongodb.com Ali Mir
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: