[SERVER-51406] Wait for failed configsvr replica set host discovery Created: 07/Oct/20  Updated: 29/Oct/23  Resolved: 07/Oct/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.7.0
Fix Version/s: 4.9.0

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

Issue Links:
Depends
Related
is related to SERVER-51397 Mongos fails to serve requests for 30... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-10-19
Participants:
Linked BF Score: 32

 Description   

As described in SERVER-51397, mongos can take up to 30s to discover that the communication to configsvr replica set node have been lost and to ends all the ongoing request to that specific node. Thus primary_config_server_blackholed_from_mongos.js needs to waits for the mongos to be aware of the failed node before to route commands through it.



 Comments   
Comment by Githook User [ 07/Oct/20 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-51406 Wait for failed configsvr replica set host discovery
Branch: master
https://github.com/mongodb/mongo/commit/e370b1577497516d9c488d0c58e2e13b5b7800be

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