Create commands to replace current shell development prototypes:
{ tagShard : <shard-name>, tag: [tags]/<tag> } { untagShard : <shard-name>, tag: [tags]/<tag> }} { tagChunks : <ns>, range: { min/max : {<shard-key value>} }, tag: <tag>}
The tagChunk commands should validate that the namespace is valid, that the tag exists on some shard, that the min/max value is of the correct format and defines a value in the shard-key (if a prefix is used then $Min/MaxKey can be added for the missing fields), and that there are not overlapping ranges; if any of these validations fail then the commands should return an error.
These commands are critical to support other clients than the shell, like all drivers, and is necessary for centralizing logic and behavior at the mongos codebase.
The commands should also make sure that chunk boundaries line up with the new tags ranges.
- is depended on by
-
SERVER-6943 addTagRegion/addShardTag fail with 3 config server sharded clusters
- Closed
- is duplicated by
-
SERVER-10262 mongos assertion triggers "Assertion: 16634:field names of bound { yearMonthDay: MinKey } do not match those of keyPattern { _id: 1.0 }"
- Closed
-
SERVER-12603 Improve handling of wrong tag ranges
- Closed
-
SERVER-22189 addShardTag &addTagRange not available in runCommand
- Closed
- is related to
-
SERVER-19131 clusterManager role does not have permission for adding tag ranges
- Closed
-
SERVER-22108 MongoDB does not raise an exception when creating tags with overlapping ranges.
- Closed
-
SERVER-16340 Mongo shell javascript sharding admin functions not available in drivers
- Closed
-
SERVER-6999 Embedded "dot-notation" fields broken for tag based balancing
- Closed
-
SERVER-19150 sh.addTagRange does not check for data completeness
- Closed
- related to
-
SERVER-6349 sh.addTagRange() doesn't valid namespace is sharded, nor min/max are valid for the shard key, nor shards contain the tag
- Closed
-
SERVER-6350 Do not allow completely removing tag from all shards if currently in use (in config.tags collection)
- Closed
-
SERVER-12141 Cannot create appropriate tag ranges with compound shard key
- Closed
-
SERVER-6352 Add sh.removeTagRange(ns, min, max, tag)
- Closed
-
SERVER-6574 Make error message better when tags are in the wrong format
- Closed
-
SERVER-9371 addTagRange should prevent min and max being the same
- Closed