I have 3 config server and two shards. Each shard has a primary, secondary and an arbiter.
This is running with the following mongod settings:
storageEngine=wiredTiger
wiredTigerJournalCompressor=zlib
wiredTigerCollectionBlockCompressor=zlib
The mongos instance created the following log entries below about not being able to get a lock during the sharding balancing. All the data can be queried fine however.
Also all seems fine with sh.status()
command:
shards:
{ "_id" : "ib3_prod_rs0", "host" : "ib3_prod_rs0/ip-10-0-13-119.ec2.internal:27017,ip-10-0-21-50:27017" }
{ "_id" : "ib3_prod_rs1", "host" : "ib3_prod_rs1/ip-10-0-6-138:27017,ip-10-0-8-202.ec2.internal:27017" }
balancer:
Currently enabled: yes
Currently running: yes
Balancer lock taken at Wed Apr 01 2015 00:00:49 GMT+0000 (UTC) by 54.163.248.60:27017:1427843620:1804289383:Balancer:1681692777
Failed balancer rounds in last 5 attempts: 0
Migration Results for the last 24 hours:
No recent migrations
How can I debug what is going on?
2015-03-31T23:41:06.542+0000 I SHARDING [Balancer] moveChunk result: { ok: 0.0, errmsg: "could not acquire collection lock for cubes_prod.pushqueues to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: could not get status from ser...", $gleStats: { lastOpTime: Timestamp 0|0, electionId: ObjectId('551b29f564e83f84e725241e') } } 2015-03-31T23:41:06.543+0000 I SHARDING [Balancer] balancer move failed: { ok: 0.0, errmsg: "could not acquire collection lock for cubes_prod.pushqueues to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: could not get status from ser...", $gleStats: { lastOpTime: Timestamp 0|0, electionId: ObjectId('551b29f564e83f84e725241e') } } from: ib3_prod_rs1 to: ib3_prod_rs0 chunk: min: { UserKey: MinKey } max: { UserKey: 0 }