[SERVER-10038] sh.status() hangs forever if first configdb is unreachable Created: 26/Jun/13  Updated: 05/May/17  Resolved: 05/May/17

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Christian Hergert Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian Linux 6.0 (Squeeze) / 10gen apt repository


Issue Links:
Depends
Operating System: ALL
Steps To Reproduce:

1) Start three configdb servers.
2) Start mongos with --configdb server1:27019,server2:27019,server3:27019
3) Connect to mongos with mongo shell.
4) Run sh.status(), verify success.
5) Disable networking on server1 to create a network partition.
6) Run sh.status(), expect infinite hang.

Participants:

 Description   

Running sh.status() from a mongos instance configured with three configdb servers can hang forever (tested hang for about 5 minutes), if the first configured configdb server is unreachable.

Various monitoring systems use this command to check status and therefore causes them to hang.

It should be noted that queries to shards continue to work normally despite the failure of sh.status().



 Comments   
Comment by Justin Cohler [ 05/May/17 ]

This was addressed by config servers as replica sets in MongoDB >= 3.2. Mirrored config servers are deprecated and we do not intend to make any further improvements in our existing roadmap.

Generated at Thu Feb 08 03:22:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.