[SERVER-22768] Handle transitioning from cancelled to cancelled in NetworkInterfaceASIO Created: 19/Feb/16  Updated: 22/Feb/16  Resolved: 19/Feb/16

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 3.3.1
Fix Version/s: 3.3.2

Type: Bug Priority: Major - P3
Reporter: Mira Carey Assignee: Mira Carey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 10 (02/19/16)
Participants:
Linked BF Score: 0

 Description   

We can be cancelled multiple times, which triggers multiple transitions to cancelled, which triggers an invariant that we not transition to the same state.

Add a condition at the top of transitionToState which catches this case and treats the transition as a noop.



 Comments   
Comment by Githook User [ 19/Feb/16 ]

Author:

{u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}

Message: SERVER-22768 fix ASIO cancelled to cancelled

When operations transition from kCancelled to kCancelled, as when an
operation is cancel()ed twice, an invariant fires. We should handle
that case specially and treat the transition as a noop.
Branch: master
https://github.com/mongodb/mongo/commit/401ad1915d6b7edde97c290f82cecab4a26880df

Generated at Thu Feb 08 04:01:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.