[SERVER-74260] Fix DDLLockManager error message returned when hitting lock timeout Created: 22/Feb/23 Updated: 29/Oct/23 Resolved: 06/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pol Pinol |
| 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 EMEA 2023-03-06 | ||||
| Participants: | |||||
| Linked BF Score: | 105 | ||||
| Description |
|
The error message returned when hitting the timeout waiting for a DDLLock incorrectly attaches the reason of the timed out acquisition indicating it as the reason set by the coordinator currently holding the lock (that instead should be nsLock->reason). |
| Comments |
| Comment by Githook User [ 06/Mar/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |