Shard start mongos error for the first time, who can tell me how this

Mongos configuration file
# mongod. Conf

Sharding:
ConfigDB: mdbconfig/192.168.139.134:21000192168 139.135:21000192168 139.136:21000

Net:
BindIp: 192.168.139.134, 127.0.0.1
Port: 20000


SystemLog:
Destination: the file
LogAppend: true
Path:/u01/mongo/mongos/log/configsrv log

ProcessManagement:
The fork: true

2017-12-20T01:12:26.018-0800 W SHARDING [mongosMain] Error initializing sharding state, sleeping for 2 seconds and trying again :: caused by :: Unauthorized: Error loading clusterID :: caused by :: not authorized on config to execute command { find: "version", readConcern: { level: "majority", afterOpTime: { ts: Timestamp(0, 0), t: -1 } }, maxTimeMS: 30000, $readPreference: { mode: "nearest" }, $replData: 1, $clusterTime: { clusterTime: Timestamp(0, 0), signature: { hash: BinData(0, 0000000000000000000000000000000000000000), keyId: 0 } }, $configServerState: { opTime: { ts: Timestamp(0, 0), t: -1 } }, $db: "config" }
2017-12-20T01:12:26.018-0800 I SHARDING [shard registry reload] Periodic reload of shard registry failed :: caused by :: Unauthorized: could not get updated shard list from config server due to not authorized on config to execute command { find: "shards", readConcern: { level: "majority", afterOpTime: { ts: Timestamp(0, 0), t: -1 } }, maxTimeMS: 30000, $readPreference: { mode: "nearest" }, $replData: 1, $clusterTime: { clusterTime: Timestamp(0, 0), signature: { hash: BinData(0, 0000000000000000000000000000000000000000), keyId: 0 } }, $configServerState: { opTime: { ts: Timestamp(0, 0), t: -1 } }, $db: "config" }; Will retry after 30 s
The 2017-12-20 T01: if then. 018-0800 I an ASIO [NetworkInterfaceASIO ShardRegistry - 0] Successfully connected to 192.168.139.134:21000, took 1 ms (21000) 4 connections now open to 192.168.139.134:
2017-12-20T01:12:26.019-0800 W SHARDING [replSetDistLockPinger] pinging failed for distributed lock pinger :: caused by :: Unauthorized: not authorized on config to execute command { findAndModify: "lockpings", query: { _id: "mongodb1:20000:1513761146:7138224804712661548" }, update: { $set: { ping: new Date(1513761146014) } }, upsert: true, writeConcern: { w: "majority", wtimeout: 15000 }, maxTimeMS: 30000, $replData: 1, $clusterTime: { clusterTime: Timestamp(0, 0), signature: { hash: BinData(0, 0000000000000000000000000000000000000000), keyId: 0 } }, $configServerState: { opTime: { ts: Timestamp(0, 0), t: -1 } }, $db: "config" }
The 2017-12-20 T01: if then. 218-0800 I an ASIO [NetworkInterfaceASIO ShardRegistry - 0] Connecting to 192.168.139.135:21000
The 2017-12-20 T01: if then. 219-0800 I an ASIO [NetworkInterfaceASIO ShardRegistry - 0] Successfully connected to 192.168.139.135:21000, took 1 ms (1 connections now open to 192.168.139.135:21000)
The 2017-12-20 T01: if then. 420-0800 I an ASIO [NetworkInterfaceASIO ShardRegistry - 0] Connecting to 192.168.139.136:21000

CodePudding user response:

A keyfile start mongos config mongod with unity

CodePudding user response:

Thank you, I try, can't their replicate sets with their respective keyfile, I look at the official documentation deploy it as also didn't remind to use the same keyfile

CodePudding user response:

Mongos want and config communication config and mongos to mongod communication and monogd communication to communication between the config

These internal communication depends on keyfile

CodePudding user response:

reference rucypli reply: 3/f

config and config mongos to communication to communication and mongod mongos to config and monogd communication to communication between

These internal communication on keyfile all

Ok, have no problem, thank you, and then ask a question, directing a shard disaster how deployment

CodePudding user response:

Each shard is a set of copy of a copy of the set is highly available

CodePudding user response:

reference 5 floor rucypli reply:

each shard is a set of copy of a copy of the set is highly available

Built this I know, but must be in the same room, that if you need to how to deal with disaster preparedness in the other room

CodePudding user response:

Across the room set up copy set

CodePudding user response:

refer to 7th floor rucypli response:

copy across the room to build set is fine

Then I shard is again on different machines, different ground disaster preparedness to save resources, can put the replicate set in one machine

CodePudding user response:

refer to the eighth floor qq_25157419 response:

Quote: refer to 7th floor rucypli response:

Across the room set up copy set is fine

Then I shard is again on different machines, different ground disaster preparedness to save resources, you can put replicate set on a machine

Replicate set on a machine loses the high availability for this outage is equivalent to a shard is unavailable
The right thing to do is cross the deployment

CodePudding user response:

references 9 f rucypli response:

Quote: refer to the eighth floor qq_25157419 response:

Quote: refer to 7th floor rucypli response:

Across the room set up copy set is fine

Then I shard is again on different machines, different ground disaster preparedness to save resources, you can put replicate set on a machine

Replicate set on a machine loses the high availability for this outage is equivalent to a shard is unavailable
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull