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

AsyncResultMerger should not retry killed operations

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.2.0
    • 3.2.3, 3.3.0
    • Sharding
    • Fully Compatible
    • ALL
    • Sharding E (01/08/16)
    • 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

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: