[SERVER-51329] Unexpected non-retryable error when shutting down a mongos server Created: 02/Oct/20  Updated: 29/Oct/23  Resolved: 12/Nov/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0, 4.4.11, 5.0.5, 5.1.1

Type: Bug Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Kshitij Gupta
Resolution: Fixed Votes: 2
Labels: sharding-nyc-subteam2, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive repro_files.zip    
Issue Links:
Backports
Related
is related to PYTHON-3016 Fix flakey tests in drivers-atlas-tes... Closed
is related to SERVER-60975 Make ReplicaSetMonitorRemoved retryable Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.1, v5.0, v4.4
Sprint: Sharding 2020-10-19, Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-22, Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19, Sharding 2021-05-03, Sharding 2021-05-17, Sharding 2021-10-18, Sharding 2021-11-01
Participants:
Case:

 Description   

Setup: v4.4.0, sharded cluster: 1 shard, 2 mongos
Scenario: 100 thread concurrently executing findOne operations, with random sleeps between 1 and 1000 milliseconds

Action: Every once in a while kill a mongos server

Expected result: mongos server that is being killed only responds with retryable errors
Actual result: mongos server returns a non-retryable error:

   {
      “ok”: 0.0, 
      “errmsg”: “Encountered non-retryable error during query :: caused by :: ReplicaSetMonitor for set shard01 is removed”, 
      “code”: 199, 
      “codeName”: “ReplicaSetMonitorRemoved”, ... 
   }



 Comments   
Comment by Githook User [ 12/Nov/21 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-51329: Fix Unexpected non-retryable error when shutting down a

(cherry picked from commit 651f4a692aa59353954d3cd18ec3572fa9bf48aa)
Branch: v4.4
https://github.com/mongodb/mongo/commit/4bcc2ba7dec6f77f0a2fd01db4ec30ba5611d630

Comment by Githook User [ 12/Nov/21 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-51329: Fix Unexpected non-retryable error when shutting down a

(cherry picked from commit 651f4a692aa59353954d3cd18ec3572fa9bf48aa)
Branch: v5.0
https://github.com/mongodb/mongo/commit/3ca34ca0320609fe62e4af461342d478247bce85

Comment by Githook User [ 12/Nov/21 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-51329: Fix Unexpected non-retryable error when shutting down a

(cherry picked from commit 651f4a692aa59353954d3cd18ec3572fa9bf48aa)
Branch: v5.1
https://github.com/mongodb/mongo/commit/3df2c98107f71668cf8058a1f6cabfc0576c835e

Comment by Githook User [ 12/Nov/21 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-51329: Fix Unexpected non-retryable error when shutting down a
Branch: master
https://github.com/mongodb/mongo/commit/651f4a692aa59353954d3cd18ec3572fa9bf48aa

Generated at Thu Feb 08 05:25:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.