[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: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.0, v3.6, v3.4
|
||||||||||||||||
| Sprint: | Sharding 2018-07-16 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| 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: |
| Comment by Githook User [ 11/Jul/18 ] |
|
Author: {'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}Message: (cherry picked from commit 80c7c825a44cf99b17e81f4233445c7ab1927706) |
| Comment by Githook User [ 11/Jul/18 ] |
|
Author: {'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}Message: (cherry picked from commit 80c7c825a44cf99b17e81f4233445c7ab1927706) |
| Comment by Githook User [ 11/Jul/18 ] |
|
Author: {'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}Message: (cherry picked from commit 80c7c825a44cf99b17e81f4233445c7ab1927706) |
| Comment by Githook User [ 11/Jul/18 ] |
|
Author: {'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}Message: |
| 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 . |