Update ReshardingOplogFetcher::_reschedule to use AsyncTry

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • 200
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current implementation of ReshardingOplogFetcher::_reschedule can lead to a variable length future chains as the function can recursively call itself. Debug builds will hit an invariant if the future chain length reaches 32.

      Update to use AsyncTry instead of recursively calling itself.

              Assignee:
              Ben Gawel
              Reporter:
              Ben Gawel
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: