Have ReshardingCollectionCloner retry cloning on retryable errors from the donor shards

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2021-01-11
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Since the RecipientStateMachine is responsible for accumulating the mongo::Futures returned from multiple components, it is simpler for RecipientStateMachine if it can assume any errors are fatal for the resharding operation. That is, the RecipientStateMachine machine won't be responsible for restarting a particular component on a retryable error from a donor shard and instead each individual component is responsible for restarting itself. This likely would be implemented by using AsyncTry within the run() method of each of the components.

            Assignee:
            Max Hirschhorn
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: