[SERVER-66745] POC - Take change collection lock at AutoGetCollection Created: 25/May/22 Updated: 29/Oct/23 Resolved: 25/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Rishab Joshi (Inactive) | Assignee: | Rishab Joshi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-2334-m1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: | |
| Story Points: | 10 |
| Description |
|
This POC was about introducing a way to lock the change collection before entering the timestamped unit of work.
Essentially taking the change collection lock within the AutoGetChangeCollection().
The POC work is here: https://spruce.mongodb.com/version/62895d357742ae5ac3399275/changes?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC
Ultimately, it was decided to not go with this path as this solution is prone to deadlocks and is difficult to debug.
An alternate suggestion has been proposed here: https://jira.mongodb.org/browse/SERVER-66715 |
| Comments |
| Comment by Rishab Joshi (Inactive) [ 25/May/22 ] |
|
The POC work and decision is available in the description of this ticket. |