MongoDB learning-error and Solutions

-- An error is returned when shardcollection is created.

Mongos> dB. runcommand ({shardcollection: 'test. test', key: {_ ID: 1 }})

{

"Assertion": "invalid parameter: expected an object ()",

"Assertioncode": 10065,

"Errmsg": "DB assertion failure ",

"OK": 0

-- Cause: the replset option is added when mongod is started, so that the Master cannot be found.

-- Solution: restart mongod and cancel the replset option.

 

Certificate -------------------------------------------------------------------------------------------------------------------------------------

 

-- Auto sharding fails because the server time is not synchronized.

Fri Jan 6 12:46:09 [balancer] Caught exception while doing balance: Error Checking clock skew of cluster 10.192.9.110: 20000, 10.192.

136.242: 20000, 10.192.9.90: 20000: caused by: 13650 clock skew of the cluster 10.192.9.110: 20000, 10.192.136.242: 20000, 10.192.9.90:

20000 is too far out of bounds to allow distributed locking.

 

Fri Jan 6 13:14:24 [conn2] Warning:-cmd: {splitchunk: "test1.test1", keypattern: {_ ID: 1.0}, Min: {_ ID: min

Key}, Max: {_ ID: maxkey}, from: "10.192.9.110: 10000", splitkeys: [{_ ID: 0.0}], shardid: "test1.test1-_ id_minkey ", configdb :"

10.192.9.110: 20000, 10.192.136.242: 20000, 10.192.9.90: 20000 "} result: {errmsg:" error locking distributed lock for split.: caused

By: 13651 error checking clock skew of cluster 10.192.9.110: 20000, 10.192.136.242: 20000, 10.192.9... ", OK: 0.0}

 

CP/usr/share/zoneinfo/GMT/etc/localtime

Ntpdate 10.192.0.12 -- Time Server

Bytes ---------------------------------------------------------------------------------------------------------------------

 

-- Config service has been stopped for no reason

Mon Jan 9 07:04:56 [balancer] movechunk result: {cause: {assertion: "Can't take a write lock while out of disk space", assertioncode: 14031, errmsg: "DB assertion failure", OK: 0.0}, errmsg: "movechunk failed to engage to-shard in the data transfer: DB assertion failure", OK: 0.0}

Mon Jan 9 07:04:56 [balancer] balancer move failed: {cause: {assertion: "Can't take a write lock while out of disk space", assertioncode: 14031, errmsg: "DB assertion failure", OK: 0.0}, errmsg: "movechunk failed to engage to-shard in the data transfer: DB assertion failure", OK: 0.0} from: S2: s1 Chunk: {_ ID: "test. test _ id_16690.0 ", lastmod: Timestamp 3000 | 1, NS:" test. test ", Min: {_ ID: 16690.0}, Max: {_ ID: 50791.0}, shard:" S2 "}

Cause: 10.192.9.90 the disk space is full.

Solution: increase disk space