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

      Each resharding operation copies its donors' full session history to the recipient, with no filter by collection. When two operations do this at the same time, they write overlapping session state. The end state must be correct.

      Scenarios:

      • Different snapshots: run retryable writes on L at txnNumbers 8 and 9 between the start of A and the start of B, so each operation's cloner sees a different latest txnNumber. Force each cloner to go first in turn. L should end at txnNumber 9, retrying 7 gets TransactionTooOld, and nothing is duplicated.
      • Applier behind the other cloner: hold A's applier until B's cloner has recorded L at a higher txnNumber, then release it. A's collection should contain each of those writes exactly once.
      • Multi-document transactions: a committed transaction on L that writes to A and B. Run it as small, large and prepared. Each collection should contain that transaction's documents exactly once. Separately, run a cross-shard transaction that writes to A and to a collection the recipient already owns. The recipient's committed-transaction state for L should survive B's cloner.
      • Recipient is also a donor: start B first so that its cloner writes session history on a shard, then start A with that shard as a recipient. A's cloner should complete and L should be unchanged.
      • Another operation kills transactions while a cloner holds a session: pause A's cloner while it holds a session on a shard that is a donor for B. Then drive B to the point where it aborts unprepared transactions on that shard. A's cloner should complete without being interrupted.

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

              Created:
              Updated:
              Resolved: