[SERVER-50620] Make ChunkHelper.moveChunk retryable on LockBusy error Created: 28/Aug/20 Updated: 29/Oct/23 Resolved: 03/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Eric Maynard |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2020-09-07 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 12 | ||||||||
| Description |
|
Add ErrorCodes::LockBusy to the list of acceptable errors in ChunkHelper.moveChunk(). |
| Comments |
| Comment by Githook User [ 04/Sep/20 ] |
|
Author: {'name': 'Eric Maynard', 'email': 'eric.maynard@mongodb.com', 'username': 'ermay12'}Message: |
| Comment by Max Hirschhorn [ 28/Aug/20 ] |
|
I believe LockBusy would only arise during the stepdown suite and we'd otherwise never fail to unlock the distributed lock. We can guard the acceptable code with runningWithStepdowns && in that case. |