[SERVER-44476] Include number of jumbo chunks remaining in output of removeShard Created: 07/Nov/19 Updated: 29/Oct/23 Resolved: 26/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.2, 4.0.14, 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | 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 | ||||||||||||||||||||
| Backport Requested: |
v4.2, v4.0
|
||||||||||||||||||||
| Sprint: | Sharding 2019-12-02 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently, if removeShard is called while the shard is still draining the output of the command is
The only place the number of jumbo chunks that remains is reported is in the config server logs. It would be more helpful if we also reported this number in the command output as well. We do a find on config.chunks in order to report the number of chunks remaining, so it should be easy to search for those entries which have 'jumbo: true'. |
| Comments |
| Comment by Githook User [ 28/Nov/19 ] |
|
Author: {'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@10gen.com'}Message: (cherry picked from commit 11754f469d36468e7c649cb9c052230614e4cb44) |
| Comment by Githook User [ 27/Nov/19 ] |
|
Author: {'email': 'marcos.grillo@10gen.com', 'name': 'Marcos José Grillo Ramírez'}Message: (cherry picked from commit 11754f469d36468e7c649cb9c052230614e4cb44) |
| Comment by Githook User [ 22/Nov/19 ] |
|
Author: {'email': 'marcos.grillo@10gen.com', 'name': 'Marcos José Grillo Ramírez'}Message: |
| Comment by Josef Ahmad [ 15/Nov/19 ] |
|
Very useful from a TS perspective. |
| Comment by Kaloian Manassiev [ 15/Nov/19 ] |
|
evin.roesle, I just remembered that this is also something that the Cloud team has previously asked for as well, so they can expose in the UI that the shard cannot be removed without further manual intervention. |
| Comment by Evin Roesle [ 14/Nov/19 ] |
|
Hi linda.qin, josef.ahmad I'm a product manager on Aly's team. I was hoping to get your input on this. Would this information be helpful to the TSE team? |