-
Type:
Task
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Sharding NYC 2022-05-30
The following commands do not seem to work on a sharded cluster, I ran them by hand through the shell:
sh.updateZoneKeyRange("foo.bar", { "key": { "$minKey": 1 } }, { "key": { "$maxKey": 1 } }, "zone") sh.updateZoneKeyRange("foo.bar", { "key": { "$minKey": 1 } }, { "key": 50 }, "zone") sh.updateZoneKeyRange("foo.bar", { "key": 50 }, { "key": { "$maxKey": 1 } }, "zone")
as it complains about
"errmsg" : "min: { key: { $minKey: 1.0 } } should be less than max: { key: { $maxKey: 1.0 } }",
I found https://jira.mongodb.org/browse/SERVER-32862, where there is a comment "Another interesting aspect is the following" about a similar bug (different from the main bug of that issue that was fixed).
Using MinKey/MaxKey like in https://www.mongodb.com/docs/manual/reference/method/sh.updateZoneKeyRange/ does work.
- is related to
-
SERVER-32862 sh.addShardToZone() allows unusual (invalid?) chunks to be created
-
- Closed
-
-
SERVER-34644 Disable `DollarPrefixedFieldName` checks for moveChunk/mergeChunks
-
- Closed
-