[DOCS-8928] mongos and shards will become unusable if contact is lost with all CSRS config server nodes for more than 30 seconds Created: 28/Sep/16 Updated: 30/Oct/23 Resolved: 31/Jul/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 28 weeks, 2 days ago | ||||||||
| Epic Link: | 3.4: Sharding Updates | ||||||||
| Description |
|
If mongos loses network contact with all nodes from the CSRS config server set (both primary and secondaries), the replica set monitor will deem this set as as 'unusable' and will stop monitoring it. From this point onward all operations which need to access some config server metadata will begin failing with the following error:
This includes the refresh of the list of shards, which needs to be read from the config server metadata. Therefore, currently there is no procedure to restart or retry monitoring of the config server set and the only recourse is to restart mongos. |
| Comments |
| Comment by Githook User [ 31/Jul/17 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'username': 'kay-kim', 'name': 'kay'}Message: |
| Comment by Githook User [ 31/Jul/17 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'username': 'kay-kim', 'name': 'kay'}Message: |
| Comment by Githook User [ 31/Jul/17 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'username': 'kay-kim', 'name': 'kay'}Message: |