[SERVER-43990] A command to confirm that all chunks have been moved to the right zone after the initial split Created: 14/Oct/19 Updated: 29/Oct/23 Resolved: 25/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alyson Cabral (Inactive) | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2019-11-18, Sharding 2019-12-02 | ||||
| Participants: | |||||
| Description |
|
There is a grey area between the chunks be created and when they move and are owned by the appropriate zone. Users would like to confirm that the chunks are placed according to the zone definition before inserting data. I recognize that this happens very quickly in the new initial split model, but this question still comes up fairly frequently. I'd like to provide an easy way for atlas/users to check that it's safe to begin data insertion. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 25/Nov/19 ] |
|
The changes on the output can be tracked with the following ticket: |
| Comment by Githook User [ 21/Nov/19 ] |
|
Author: {'email': 'marcos.grillo@10gen.com', 'name': 'Marcos José Grillo Ramírez'}Message: |
| Comment by Sheeri Cabral (Inactive) [ 28/Oct/19 ] |
|
1. The former is proper in the scope of this ticket. I like the idea of the latter, but if it takes a long time it should be moved to its own ticket. Because the scope of this ticket is to make sure checks are in the right zone. However, I do think it is useful to verify that shards are balanced properly. 2. A cached view is good enough. The systems are constantly changing, so it doesn’t matter if it’s now, or cached from five minutes or an hour ago. |
| Comment by Kaloian Manassiev [ 21/Oct/19 ] |
|
We can easily add such command, but I would like clarify a few things around its behaviour:
|