New built a directing a cluster, replicaset + sharding cluster approach, which mongos and configsvr server is reusable, mongos query problems, only in configsvr primary that stage mongos query speed normal (3-5 seconds), other node query speed is very slow (35 seconds +);
A cluster is deployed in ali cloud; The cluster deployment deployment tests in the test environment, the speed of each node can meet the requirements, but after production deployment, not
Pray god help
Shard has launched, but no start index fragmentation
This is the cluster information
Mongos> Use the admin
Switched to the db admin
Mongos> The runCommand ({1} listshards:)
{
"Shards" : [
{
"_id" : "shard1,"
"The host" : "shard1/10.24.188.197:27001,10.26. 68.102:27001",
"State" : 1
},
{
"_id" : "shard2,"
"The host" : "shard2/10.24.197.219:27002,10.26. 68.102:27002",
"State" : 1
},
{
"_id" : "shard3,"
"The host" : "shard3/10.24.188.197:27003,10.24. 197.219:27003",
"State" : 1
}
],
"Ok" : 1
}


Mongos> Sh. The status (true)
- Sharding Status -- -- --
Sharding version: {
"_id" : 1,
"MinCompatibleVersion" : 5,
"CurrentVersion" : 6,
"ClusterId" : ObjectId (" 5 bdacb1ecabce31601525a70 ")
}
Shards:
{" _id ":" shard1 ", "the host" : "shard1/10.24.188.197:27001,10.26. 68.102:27001", "state" : 1}
{" _id ":" shard2 ", "the host" : "shard2/10.24.197.219:27002,10.26. 68.102:27002", "state" : 1}
{" _id ":" shard3 ", "the host" : "shard3/10.24.188.197:27003,10.24. 197.219:27003", "state" : 1}
The active mongoses:
Node1: {" _id ":" 27017 ", "ping" : ISODate (" the 2018-11-01 T12:34:05. 040 z "), "up" : NumberLong (9926), "waiting" : true, "mongoVersion" : "3.4.17", "advisoryHostFQDNs:" [] "node1"}
{" _id ":" node4 ", "ping" : ISODate (" the 2018-11-01 T12:34:04. 668 z "), "up" : NumberLong (1210), "waiting" : true, "mongoVersion" : "3.4.17", "advisoryHostFQDNs" : [" node4 "]}
2: {" _id ":" 27017 ", "ping" : ISODate (" the 2018-11-01 T12:34:00. 045 z "), "up" : NumberLong (9956), "waiting" : true, "mongoVersion" : "3.4.17", "advisoryHostFQDNs:"/" 2 "}
Node3: {" _id ":" 27017 ", "ping" : ISODate (" the 2018-11-01 T12:33:57. 712 z "), "up" : NumberLong (9907), "waiting" : true, "mongoVersion" : "3.4.17", "advisoryHostFQDNs" : [node3 "]}
Autosplit:
Currently enabled: yes
Balancer:
Currently enabled: yes
Currently running: no
Balancer lock seems at Thu Nov 01 2018 17:45:02 GMT + 0800 (CST) by ConfigServer: Balancer
Failed balancer rounds in the last 5 attempts: 0
Migration Results for the last 24 hours:
No recent migrations
The databases:
{" _id ":" firmmemberinfo ", "primary" : "shard3", "partitioned" : true}


Because just contact mongo time is not long, to be unfamiliar with mongo
Great god help just a little trouble

CodePudding user response:

To see if each node logs exception see between each node of the network is normal