[DOCS-11864] Zone Sharding example is misleading regarding behavior on documents outside of all tag ranges Created: 08/Jul/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Sommer | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | sharding, zones | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.5 |
| Description |
|
---------------------------- Original Descriptionhttps://docs.mongodb.com/manual/core/zone-sharding/#zones In the example, document { x : 23 }ends up on shard "Charlie". This is indeed possible. But it is not the only possibility. My testing showed that in the case of documents not covered by any of the configured tag ranges, those documents will be balanced among all shards – those with and without a tag. So the { x : 23 }could end up on shard "Charlie". But it could end up on "Alpha" or "Beta", too. Showing it on "Charlie" incorrectly implies that it could only end up there, which is not correct. Documents (again, per my testing) not falling in any tag range end up on shards with and without tags, not only on shards without tag. The example should make that clear – i.e, by showing document { x :25 }on shard alpha, and explaining why that happens. DescriptionScope of changes (files that need work and how much)Impact to other docs outside of this productMVP (work and date?)Resources (e.g. Scope Docs, Invision) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |