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

      Several operations can enter their critical sections at the same time, on shards that play different roles for each of them. Waiting between the operations must not form a cycle.

      Scenarios:

      • drive N operations into their critical sections together, both through the commit monitor and through manual commitReshardCollection
      • crossed roles: shard S1 is a donor for A and a recipient for B, and shard S2 is the reverse; both operations enter the critical section at the same time
      • one operation is blocking writes on a shard while another operation on the same shard is still trying to reach strict consistency
      • one operation's donors abort unprepared transactions while another operation is holding sessions or running clone or apply transactions on that shard

      Assert that every operation completes or aborts cleanly within the critical-section timeout, and that none hangs.

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

              Created:
              Updated:
              Resolved: