[SERVER-18728] Unable to move chunks due to error message code 8041 Created: 29/May/15  Updated: 29/May/15  Resolved: 29/May/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.6.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Wedge Martin Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Stock 2.6.10 database. 3 config svrs, 2x3.

Participants:

 Description   

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. 



 Comments   
Comment by Wedge Martin [ 29/May/15 ]

Noted. Just as an fyi, we've verified several times that each mongos can reach the config servers on the specified port. I'll move this to the user group discussion though. Thanks for the quick response!

Comment by Ramon Fernandez Marina [ 29/May/15 ]

wedge@badgeville.com, the error

"errmsg" : "exception: no primary shard configured for db: config",

indicates that this mongos can't talk to at least one of your config servers; please check network connectivity between this mongos and all your config servers, including firewall rules.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Generated at Thu Feb 08 03:48:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.