[SERVER-22027] AsyncResultMerger should not retry killed operations Created: 29/Dec/15  Updated: 21/Nov/16  Resolved: 30/Dec/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.2.0
Fix Version/s: 3.2.3, 3.3.0

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: code-and-test
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding E (01/08/16)
Participants:
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.



 Comments   
Comment by Githook User [ 13/Jan/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22027 Sharding should not retry killed operations

This change introduces a different interruption code (11602) which will be
used to kill operations during replication primary stepdown so the config
server retry logic can differentiate them from user-killed operations.
Branch: v3.2
https://github.com/mongodb/mongo/commit/ce0f41c5ace60ba89e55c5244cdaf79c5d78c503

Comment by Githook User [ 30/Dec/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22027 Sharding should not retry killed operations

This change introduces a different interruption code (11602) which will be
used to kill operations during replication primary stepdown so the config
server retry logic can differentiate them from user-killed operations.
Branch: master
https://github.com/mongodb/mongo/commit/e49a2a16fb4b337d7ed1b0ec8d766f281741d8bf

Comment by Githook User [ 30/Dec/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: Revert "SERVER-22027 Sharding should not retry killed operations"

This reverts commit 5d2d6e209acd862324612c7f9c41d65940f8dcba.
Branch: master
https://github.com/mongodb/mongo/commit/715e9e1cdc618dad480a7a1a73458daf6ea9ce0f

Comment by Githook User [ 30/Dec/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22027 Sharding should not retry killed operations
Branch: master
https://github.com/mongodb/mongo/commit/5d2d6e209acd862324612c7f9c41d65940f8dcba

Generated at Thu Feb 08 03:59:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.