[SERVER-47045] Add tests to check that mongos marks a mongod as failed in failure cases Created: 23/Mar/20 Updated: 29/Oct/23 Resolved: 20/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc3, 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| 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.4
|
||||||||||||
| Sprint: | Sharding 2020-04-06, Service arch 2020-04-20, Service arch 2020-05-04 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Add the following three test cases to check that mongos correctly marks a mongod as down (marks its type as unknown in its server description): 1. After mongos receives one isMaster response from a node, cease all isMaster replies on this node. MongoS should mark this node as down after connectTimeoutMS + maxAwaitTimeMS. Add a fourth test case to check that mongos does not mark a mongod as down if mongod responds with 'ok : 1' but without the 'moreToCome' bit set. This test should verify that the client does not mark the server unknown and continues monitoring the mongod after it ends the isMaster stream. |
| Comments |
| Comment by Githook User [ 27/Apr/20 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: (cherry picked from commit ae194cbab3b84a145d2e5b585c4dd0a261830675) |
| Comment by Githook User [ 20/Apr/20 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |
| Comment by Shane Harvey [ 23/Mar/20 ] |
|
Some notes on each test: |