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

AsyncResultMerger should not retry killed operations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.0
    • Fix Version/s: 3.2.3, 3.3.0
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding E (01/08/16)
    • Linked BF Score:
      0

      Description

      As part of the changes to make sharding more robust in the presence of CSRS config server stepdowns we made most operations retriable on these error codes.

      This is problematic because we have no way of differentiating between interruptions due to the actual operation being killed or due to the primary stepping down, so now operations fail to get killed as experienced by failures in jstests/sharding/features3.js.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: