Migration donor may fail to deliver abort to a recipient

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1022
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v9.0
    • ClusterScalability 31Aug-14Sep
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a migration is aborted, the donor may fail to notify the recipient, because the notification is sent on an OperationContext that has interrupted.

      A recipient blocked waiting for orphan cleanup then never learns of the abort and waits the full 300s timeout, stalling other operations. See BF-43315 for more details.

            Assignee:
            Brett Nawrocki
            Reporter:
            Kruti Shah
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: