[SERVER-7553] mongos crashes when configdb is not listening to the port but waits when it cannot resolve the DNS Created: 05/Nov/12  Updated: 10/Aug/16  Resolved: 20/Jul/16

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

Type: Improvement Priority: Major - P3
Reporter: Alon Horev Assignee: Misha Tyulenev
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-16044 Add option: On startup mongos should ... Closed
Related
related to SERVER-25029 Segmentation fault in mongos when con... Closed
related to SERVER-25135 Mongos on startup becomes unusable if... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 18 (08/05/16)
Participants:

 Description   

I believe it would be more consistent and robust to perform retries even when the ip is reachable although the configdb hasn't come up yet, and not crash.

Update: see more details in the description in SERVER-16044 (duplicate of this)



 Comments   
Comment by Misha Tyulenev [ 18/Jul/16 ]

ger.hartnett I tested mongos behavior in master and 3.2 - in both cases mongos will be waiting for the config servers specified in the --configdb parameter.
However there is a bug in master - I'm addressing it separately in SERVER-25135.
Please confirm that 3.2 works as expected so I can close this issue.

Comment by Andy Schwerin [ 14/Jul/16 ]

We need to re-test, to see if this is still the behavior in 3.2 and on master. I did some cursory testing, and it looked to me like this bug had gone away on 3.2. misha.tyulenev will re-test.

Comment by Andy Schwerin [ 12/Oct/15 ]

spencer maintains that this is also a problem after SERVER-1448.

Comment by Andy Schwerin [ 31/Aug/15 ]

The crash appears to happen during checkConfigServersConsistent. At master, new sharded clusters use replica sets for config servers as part of SERVER-1448. I'm curious to know if/how this problem manifests there, since they do not need to perform config server consistency checks.

Comment by Greg Studer [ 08/Jan/13 ]

Confirmed.

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