Loading...

XML

Word

Printable

JSON

Operating System:
ALL
Steps To Reproduce:

Hide

2.6 shell, 2.4 config DB/shards
sh.addShardTag("shard0000","ZERO");
/* no effect */
db.getSiblingDB("config").shards.update(db.getSiblingDB("config").shards.update({_id:"shard0000"},{$addToSet:{"tags":"ZERO"}}
... )
WriteResult({
"writeError" :
{ "code" : undefined, "errmsg" : "no such cmd: update" }
})

Show
2.6 shell, 2.4 config DB/shards sh.addShardTag("shard0000","ZERO"); /* no effect */ db.getSiblingDB("config").shards.update(db.getSiblingDB("config").shards.update({_id:"shard0000"},{$addToSet:{"tags":"ZERO"}} ... ) WriteResult({ "writeError" : { "code" : undefined, "errmsg" : "no such cmd: update" } })
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

It seems that mongo shell helpers in 2.6 send updates as 2.6 update commands, but 2.4 config DB doesn't know what those are.

This makes some sharding helpers like sh.addShardTag() silently fail.

duplicates

SERVER-12743 shell doesn't test server version on reconnect