-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.3.10
-
Component/s: Sharding
-
None
-
ALL
Setup: v3.2 shards, v3.2 mongos, v3.4 config servers
assert.soon failed, msg:Waited too long for lock balancer to unlock doassert@src/mongo/shell/assert.js:15:14 assert.soon@src/mongo/shell/assert.js:176:13 sh._waitForDLock@src/mongo/shell/utils_sh.js:251:1 sh.waitForBalancer@src/mongo/shell/utils_sh.js:318:13 sh.stopBalancer@src/mongo/shell/utils_sh.js:175:9 _extendWithShMethods/</self[fn]@src/mongo/shell/shardingtest.js:194:28 _configureCluster@src/mongo/shell/shardingtest.js:208:13 ShardingTest@src/mongo/shell/shardingtest.js:1310:9 @/mnt/hdd/mongo-copy/jstests/multiVersion/new_mongos_old_mongod.js:5:18 @/mnt/hdd/mongo-copy/jstests/multiVersion/new_mongos_old_mongod.js:1:2
This is because the stopBalancer code assumes that if balancerStop command is not found, then it should use the old logic that involves waiting for balancer lock to be freed ( https://github.com/mongodb/mongo/blob/2464cdaf2a2c523ea1c116da60c27ad12e580a09/src/mongo/shell/utils_sh.js#L172). And this will never happen since v3.4 config servers will never release them
- is related to
-
DOCS-8140 Document the new balancer control commands and the deprecation of the old shell's balancer control scripts
-
- Closed
-