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

Consider sorting documents by recordId before applying entries on secondaries

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL

      Currently each applier thread receives a bunch of documents to insert (in the form of oplog entries). With recordIdsReplicated:true collections, the secondaries receive recordIds to use in the oplog entries, so they don't need to assign recordIds anymore. This means that the documents being inserted may not actually be in recordId order.

      SERVER-88392 tracks a dassert being triggered as a result.

      However, we should see if maybe we can sort the documents first by recordId to see if we can improve performance (making it different from the correctness issue in SERVER-88392).

            Assignee:
            Unassigned Unassigned
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: