[SERVER-38933] currentOp is not resilient to drop shard Created: 10/Jan/19  Updated: 29/Oct/23  Resolved: 14/Jan/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.7, 4.1.7

Type: Bug Priority: Major - P3
Reporter: Martin Neupauer Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: Query 2019-01-14, Query 2019-01-28
Participants:

 Description   

currentOp is using a stale cluster view and it tries to contact non existing shard.



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

Author:

{'name': 'Martin Neupauer', 'email': 'martin.neupauer@mongodb.com', 'username': 'MartinNeupauer'}

Message: SERVER-38933 currentOp is not resilient to drop shard

(cherry picked from commit 08408f78930ace30f5a8cc0823b41b7d7798a24c)
Branch: v4.0
https://github.com/mongodb/mongo/commit/9583488d4e504d1901c834a54a038dbbc52998d0

Comment by Githook User [ 14/Jan/19 ]

Author:

{'username': 'MartinNeupauer', 'email': 'martin.neupauer@mongodb.com', 'name': 'Martin Neupauer'}

Message: SERVER-38933 currentOp is not resilient to drop shard
Branch: master
https://github.com/mongodb/mongo/commit/08408f78930ace30f5a8cc0823b41b7d7798a24c

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