ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Reshard A and B at the same time, using the same donor shards and the same recipient shard. Writes to both collections are then tagged with the same destination recipient. Each operation must still fetch and apply only its own collection's writes.

      While both operations are cloning and applying, run:

      • inserts, updates and deletes on A and B
      • multi-document transactions and retryable batches that write to both A and B
      • bulkWrite across A and B, ordered and unordered, inside and outside a transaction
      • WouldChangeOwningShard updates to A and B in one transaction
      • batched multi-deletes on both collections
      • prepared transactions that write only to A and then abort
      • writes to a third collection on the same donor that is not being resharded

      Put A into its critical section and commit it while B is still applying.

      Assert:

      • each temp collection, and later each resharded collection, contains exactly its own documents
      • neither operation's oplog buffer contains entries from the other collection or from the unrelated collection
      • B's buffer does not contain A's final oplog entry

      Variant: repeat the test with timeseries collections, under both the legacy and the viewless layouts.

            Assignee:
            Unassigned
            Reporter:
            Anja Kalaba
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: