[SERVER-14571] adding tags on 2.4 config DB from 2.6 mongo shell is no-op Created: 15/Jul/14  Updated: 10/Dec/14  Resolved: 17/Jul/14

Status: Closed
Project: Core Server
Component/s: Sharding, Shell, Write Ops
Affects Version/s: 2.6.3, 2.7.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Asya Kamsky Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12743 shell doesn't test server version on ... Backlog
Operating System: ALL
Steps To Reproduce:

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" }

})

Participants:

 Description   

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.


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