[SERVER-38384] More verbose sh.shardCollection command Created: 04/Dec/18 Updated: 06/Dec/22 Resolved: 23/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Miguel Angel Nieto | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
Hello, There are cases when sh.shardCollection takes a very long time. During that time the MongoDB Shell is hung. This is a bad user experience, since there is no information on what is happening and no estimates. Also, closing the window by mistake could probably cancel the operation after a very long wait. To provide a better user experience the sh.shardCollection should:
or
Regards. |
| Comments |
| Comment by Randolph Tan [ 11/Dec/18 ] |
|
Notes: Shard coll summary (as of 4.1.6): 1. Get distLocks for db and coll. The checkShardingIndex command by far has the potential to take a long time, since it had to scan every single document. |