Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48550

Range deletion code should allow exceptions from PlanExecutor::getNext to bubble up to the retry loop instead of swallowing them

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc9, 4.7.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v4.4
    • Sharding 2020-06-15
    • 45

      Before SERVER-43821, the query code would sometimes return PlanExecutor::FAILURE and sometimes throw an exception.

      The range deletion code was handling exceptions correctly (they would bubble up to this AsyncTry/Until), but was swallowing PlanExecutor::FAILURE

      SERVER-43821 made the query code always throw exceptions and the range deletion code always swallow them, but we should make the range deletion code actually always allow them to bubble up to the AsyncTry/Until.

      Marking as backport requested to 4.4 to fix the similar bug with swallowing PlanExecutor::FAILURE on 4.4.

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: