[SERVER-55533] Invariants in ReshardingMetrics don't account for how recipients can error during resharding Created: 25/Mar/21 Updated: 29/Oct/23 Resolved: 30/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Lamont Nelson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-autocommits | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2021-04-05 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 163 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
It is possible for recipients to be in RecipientStateEnum::kError while documents are being copied, oplog entries are being fetched, and oplog entries are being applied. This is because the RecipientStateMachine will transition to kError as soon as any data replication component encounters an operation-fatal error. The data replication components will be shut down after the RecipientStateMachine transitions to kError.
should all be updated to include RecipientStateEnum::kError as well. |
| Comments |
| Comment by Githook User [ 30/Mar/21 ] |
|
Author: {'name': 'LaMont Nelson', 'email': 'lamont.nelson@mongodb.com', 'username': 'lamontnelson'}Message: |
| Comment by Lamont Nelson [ 26/Mar/21 ] |
|
code review: https://mongodbcr.appspot.com/785850220/ |