When one of masters is unreachable all other replica sets work too slow in mongodb 2.6.11, also I can not list the databases on mongos servers, and that is because of one replica set. How to solve this problem.


I have found this https://jira.mongodb.org/browse/SERVER-7246, do they say "If you have no redundant network connection to remote site, then go to hell"?


Replica sets are individual entities unless you are sharing resources among them like CPU,RAM,Disk... running multiple mongods in a single server.

I believe your case is that on a sharded cluster scatter-gather queries speed is determined by the slowest shard, so when one shard gets slow all scatter-gather queries will turn slow.

| improve this answer | |
  • No that is not my case, all my rs members are residing on different machines, although they are virtual machines(on different esxi hosts). it takes 10+ seconds to get show collections output. – Edik Mkoyan Oct 30 '15 at 6:37
  • I have multiple data centers and a star topology. When I loose connection to that data center, slave in the hub location or central if you may, starts to work to slow, and actually all other replica sets also start to "hang" on my Yii(php) application I often see error 71 internal server error, mongos just drops most of the connections. And that is strange because I have no sharding enabled, and I have one database for each rs. – Edik Mkoyan Nov 4 '15 at 7:40

Upgrading to 3.0.7 and switching to wiredtiger solved this issue.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.