-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.1.8
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding E (01/08/16)
The shard will return an error on setShardVersion if it still has the old non-repl config server string.
Example error:
Assertion: 10429:setShardVersion failed shard: csrsUpgrade-rs0:csrsUpgrade-rs0/ren-desktop:20000,ren-desktop:20001,ren-desktop:20002 { configdb: { stored: "ren-desktop:20006,\ ren-desktop:20007,ren-desktop:20008", given: "csrs_upgrade-csrs/ren-desktop:20006,ren-desktop:20011,ren-desktop:20012" }, ok: 0.0, errmsg: "mongos specified a different config database string : stored : ren-desktop:20006,ren-deskto\ p:20007,ren-desktop:20008 vs given : csrs_upgrade-csrs/ren-...", code: 125 }
- related to
-
SERVER-21995 Queries against sharded collections fail after upgrade to CSRS due to caching of config server string in setShardVersion
- Closed