[SERVER-34897] Introduce parameter to control whether MongoS should automatically retry failed `find` commands Created: 08/May/18  Updated: 29/Oct/23  Resolved: 11/Jul/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.4.17, 3.6.7, 4.0.1, 4.1.1

Type: New Feature Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-43042 Add option to control (or disable) th... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0, v3.6, v3.4
Sprint: Sharding 2018-07-16
Participants:
Case:

 Description   

Currently MongoS unconditionally retries find commands on network and replica set errors. While this behaviour helps increase availability, there is risk where a storm of poorly constructed and heavy to execute find commands, which get retried could bring down a node of a replica set.

This ticket is to consider adding a MongoS boolean parameter, which allows customers to opt out of the retry behaviour.



 Comments   
Comment by Githook User [ 11/Jul/18 ]

Author:

{'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-34897 load() for atomic bool
Branch: v3.4
https://github.com/mongodb/mongo/commit/9b2b2510b5a2984cf2a55a1127449b34ae4a401a

Comment by Githook User [ 11/Jul/18 ]

Author:

{'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-34897 add parameter to prohibit mongos retries

(cherry picked from commit 80c7c825a44cf99b17e81f4233445c7ab1927706)
Branch: v3.4
https://github.com/mongodb/mongo/commit/9a7cb2f9d5146d1a0c0ff4cbbd21798feb30a737

Comment by Githook User [ 11/Jul/18 ]

Author:

{'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-34897 add parameter to prohibit mongos retries

(cherry picked from commit 80c7c825a44cf99b17e81f4233445c7ab1927706)
Branch: v3.6
https://github.com/mongodb/mongo/commit/774d570bfbd10b943fd1ba872f05bb1509ef7c4b

Comment by Githook User [ 11/Jul/18 ]

Author:

{'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-34897 add parameter to prohibit mongos retries

(cherry picked from commit 80c7c825a44cf99b17e81f4233445c7ab1927706)
Branch: v4.0
https://github.com/mongodb/mongo/commit/3346e3cb9609422e4f6ac41b6791e175bdfb5124

Comment by Githook User [ 11/Jul/18 ]

Author:

{'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-34897 add parameter to prohibit mongos retries
Branch: master
https://github.com/mongodb/mongo/commit/80c7c825a44cf99b17e81f4233445c7ab1927706

Comment by Eli Revach [ 01/Jul/18 ]

We like to have a hotFix or workaround as soon as you can

Thanks 

Comment by Eli Revach [ 01/Jul/18 ]

Hi

I would like to raise the severity for this to p2  , we have very heavy load system this behaves increase  timeouts as from our application side we already have such mechanism , so the overall amount of queries send to mongo twice the amount expected   , in addition ,we many time see bad   execution plan on the retry query .

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