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

[QE] Audit special read/write paths and look for potential sharding bugs

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The goal of this ticket is to audit all “special” read/write paths and see if we can identify any sharding-related bugs where MongoDB is not upholding the guarantees given by the MongoDB Server read and write semantics doc.

      “Special” read/writes paths include any read paths excluding the standard read paths used for executing FindCommandRequests on sharded clusters, and any write paths excluding the write paths used for executing update/delete on sharded clusters.

      We expect most of these "special" read/write paths are used by aggregate pipeline stages (ex. $merge).

            Assignee:
            Unassigned Unassigned
            Reporter:
            andrew.paroski@mongodb.com Drew Paroski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: