-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.6.10
-
Component/s: Sharding
-
None
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Frustrating as hell. Newly sharded database, balanacer and manual chunk moves fail due to the error:
mongos> sh.moveChunk("ksoc_django_v3.main_slamdata", { "time_stamp":ISODate("2014-10-03T16:26:04.654Z") }, "rs2" );
{
"cause" : {
"errmsg" : "exception: no primary shard configured for db: config",
"code" : 8041,
"ok" : 0
},
"code" : 8041,
"ok" : 0,
"errmsg" : "move failed"
}
What we see in the log from the balancer is:
2015-05-29T02:08:33.666+0000 [Balancer] moving chunk ns: ksoc_django_v3.main_slamdata moving ( ns: ksoc_django_v3.main_slamdata, shard: ksocdb:ksocdb/ip-172-31-35-134.us-west-2.compute.internal:27017,ip-172-31-38-25.us-west-2.compute.internal:27017,ip-172-31-42-68.us-west-2.compute.internal:27017, lastmod: 1|0||000000000000000000000000, min: { time_stamp: MinKey }, max: { time_stamp: -8260770491683947882 }) ksocdb:ksocdb/ip-172-31-35-134.us-west-2.compute.internal:27017,ip-172-31-38-25.us-west-2.compute.internal:27017,ip-172-31-42-68.us-west-2.compute.internal:27017 -> rs2:rs2/172.31.45.160:27017,172.31.45.161:27017,172.31.45.162:27017
2015-05-29T02:08:33.672+0000 [Balancer] moveChunk result: { errmsg: "exception: no primary shard configured for db: config", code: 8041, ok: 0.0 }
2015-05-29T02:08:33.673+0000 [Balancer] balancer move failed: { errmsg: "exception: no primary shard configured for db: config", code: 8041, ok: 0.0 } from: ksocdb to: rs2 chunk: min: { time_stamp: MinKey } max: { time_stamp: -8260770491683947882 }
2015-05-29T02:08:33.758+0000 [Balancer] distributed lock 'balancer/ip-172-31-44-41:27017:1432863582:1804289383' unlocked.