[SERVER-55686] Prevent resharding coordinator document from exceeding 16MB BSON size limit Created: 01/Apr/21 Updated: 29/Oct/23 Resolved: 03/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-error-flow, post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v5.0
|
||||
| Sprint: | Sharding 2021-06-14, Sharding 2021-05-31 | ||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
Donor and recipient shards periodically update the config.reshardingOperations document on the config server as part of their state changes. Most of the DonorShardContext and RecipientShardContext types are fixed in size. The exception to this for both donor and recipient shards is the abortReason. To prevent the situation where multiple participants have an abortReason causing the update to fail with BSONObjectTooLarge, the donor and recipient shards must truncate their abortReason in the update to the config.reshardingOperations collection. Things to consider:
|
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 07/Jun/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |
| Comment by Githook User [ 03/Jun/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |