Ensure that there are no ongoing transactions when removing a participant shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Cluster Scalability
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Removing a shard acting as a participant (not coordinator) in a transaction can lead to an inability to commit or abort the transaction after the removal. Therefore, it must be ensured that the removeShard operation only proceeds when all ongoing transactions finish on participants.

            Assignee:
            Unassigned
            Reporter:
            Robert Sander
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: