[SERVER-58926] ReshardingDonor should not try to set the stop time of the critical section if it the critical section was already released Created: 28/Jul/21 Updated: 29/Oct/23 Resolved: 29/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.3, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Sharding 2021-08-09 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 160 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
If the donor gets a transient error after releasing the critical section (and setting stop on critical section time interval in the resharding metrics) it will try to set the stop time again on the retry. We should check whether the critical section was actually released and only set the end time if it was. |
| 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 [ 23/Aug/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: (cherry picked from commit 07a6841c533193ec64190a870ee11672ba4d39e5) |
| Comment by Githook User [ 29/Jul/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |