[SERVER-22812] Connection lasts long time when one config server is off Created: 23/Feb/16  Updated: 03/Mar/16  Resolved: 03/Mar/16

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

Type: Bug Priority: Major - P3
Reporter: Filip Havlí?ek Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian Wheezy


Issue Links:
Duplicate
duplicates SERVER-21531 Shard's connection blocks forever whe... Closed
Operating System: Linux
Steps To Reproduce:

sharded cluster with three config servers and authentication enabled
run "poweroff" or "shutdown -h now" on one config server (not only stop service, completely shutdown the server)
test some query and you will see

Participants:

 Description   

Last week we had to make maintenance on server hardware where is one of the config servers. After server shutdown we had problems with timeouts on connections to mongos.
From tests on staging environment:
normal state

-> time echo "db.system.version.find()" | mongo --username=someuser --password=somepassword admin
MongoDB shell version: 3.0.8
connecting to: admin
{ "_id" : "authSchema", "currentVersion" : 5 }
bye
 
real	0m0.149s
user	0m0.110s
sys	0m0.030s
}}

degraded state (one server down)
-> time echo "db.system.version.find()" | mongo --username=someuser --password=somepassword admin
MongoDB shell version: 3.0.8
connecting to: admin
{ "_id" : "authSchema", "currentVersion" : 5 }
bye
 
real	0m38.845s
user	0m0.130s
sys	0m0.050s



 Comments   
Comment by Kelsey Schubert [ 03/Mar/16 ]

Hi filip.havlicek@livesport.eu,

Thank you for reporting this behavior. This issue is tracked in SERVER-21531. Since SERVER-22318 removes support for legacy config servers in 3.4, we do not intend to fix this behavior.

Please note that SERVER-17617 corrected this issue for config servers as a replica set. If you continue to run into this issue, I would recommend that you consider upgrading to 3.2 and using CSRS.

Kind regards,
Thomas

Generated at Thu Feb 08 04:01:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.