[SERVER-63910] Generalize this error message related to the critical section Created: 23/Feb/22 Updated: 29/Oct/23 Resolved: 30/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.2, 5.0.8, 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Enrico Golfieri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v5.3, v5.2, v5.0
|
||||
| Sprint: | Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04 | ||||
| Participants: | |||||
| Description |
|
This error message assumes that if the critical section is held is because there is a migration, but there are other DDL ops that also acquire it. We could write something in the line of "The critical section for $nss is acquired with reason $reason", where $nss is the namespace of the collection and $reason is obtained from the critical section object. |
| Comments |
| Comment by Githook User [ 08/Apr/22 ] |
|
Author: {'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@gmail.com', 'username': 'enricogolfieri'}Message: cherry-pick 340ead2906be74f75133c9c93e110048dc9d7b30 |
| Comment by Githook User [ 31/Mar/22 ] |
|
Author: {'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@gmail.com', 'username': 'enricogolfieri'}Message: |
| Comment by Githook User [ 29/Mar/22 ] |
|
Author: {'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@gmail.com', 'username': 'enricogolfieri'}Message: |