[SERVER-40435] A clearJumboChunk command to clear the jumbo flag Created: 02/Apr/19 Updated: 29/Oct/23 Resolved: 11/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.3, 4.0.15 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Linda Qin | Assignee: | Randolph Tan |
| Resolution: | Fixed | Votes: | 1 |
| 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-09-23, Sharding 2019-10-07, Sharding 2019-10-21 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Currently the steps to clear the jumbo flag for a chunk is quite complicated, prone to user error, and requires modifying the config database. It would be nice to support a clearJumboChunk command on the mongos, which goes through the proper versioning protocol and doesn't require direct access to the config servers. |
| Comments |
| Comment by Githook User [ 08/Jan/20 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@mongodb.com'}Message: (cherry picked from commit 546e411b72cf6f75d24b304ce9219d1f3d3a4e4f) |
| Comment by Githook User [ 07/Jan/20 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@mongodb.com'}Message: (cherry picked from commit 546e411b72cf6f75d24b304ce9219d1f3d3a4e4f) |
| Comment by Githook User [ 15/Oct/19 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@mongodb.com'}Message: |
| Comment by Githook User [ 11/Oct/19 ] |
|
Author: {'email': 'randolph@mongodb.com', 'name': 'Randolph Tan'}Message: |