Note that there are some explanatory texts on larger screens.

plurals
  1. POMongos distribute too much query to one MongoD
    primarykey
    data
    text
    <p>We have a mongodb with 2 shardings, each of the shardings has those servers:</p> <ol> <li>Shard 1: Master, running MongoD and Config server</li> <li>Shard 1-s1: Slave, running MongoD and MongoS server</li> <li>Shard 1-s2: Slave, running MongoD and MongoS and Arbiter server</li> <li>Shard 2: Master, running MongoD and Config Server</li> <li>Shard 2-s1: Slave, running MongoD and Config and MongoS server</li> <li>Shard 2-s2: Slave, running MongoD and MongoS and Arbiter server</li> </ol> <p>But the mongodb allways failed in recent days, after days of search, i find out that the MongoD runs at Shard 1(Master) always going down after reviced too many connections, other MongoD don't have this problem.</p> <p>When the S1Master's MongoD running with too many connections for about 2 hours, the 4 Mongos Server will shut down one by one. Here is the Mongos's error log(10.81.4.72:7100 runs MongoD):</p> <blockquote> <p>Tue Aug 20 20:01:52 [conn8526] DBClientCursor::init call() failed Tue Aug 20 20:01:52 [conn3897] ns: user.dev could not initialize cursor across all shards because : stale config detected for ns: user. dev ParallelCursor::_init @ s01/10.36.31.36:7100,10.42.50.24:7100,10.81.4.72:7100 attempt: 0 Tue Aug 20 20:01:52 [conn744] ns: user.dev could not initialize cursor across all shards because : stale config detected for ns: user.d ev ParallelCursor::_init @ s01/10.36.31.36:7100,10.42.50.24:7100,10.81.4.72:7100 attempt: 0</p> </blockquote> <p>I don't know why this mongod revieved so many connections, the chunks shows the sharding works well. <img src="https://i.stack.imgur.com/oXB7I.jpg" alt="enter image description here"></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload