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

Scan in record id order for dbHash

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2024-02-19, Execution Team 2024-03-04

      If a collection has replicated record ids, dbHash can scan in record id order rather than _id order. dbHash currently scans in _id order. For recordIdReplicated:true collections, we can go in natural order, as we already do for clustered collections.

      Additionally, we should include each recordId when computing the hash, to make sure that the recordIds are indeed replicated.

      In this ticket we need to handle just dbHash, not dbCheck.

      This will also help with SERVER-86167 because then our tests can rely on dbHash for correctness.

            Assignee:
            haley.connelly@mongodb.com Haley Connelly
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: