[SERVER-69463] Refresh the locking requirements in the source files documentation Created: 06/Sep/22 Updated: 14/Aug/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | documentation, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Some of these have gone stale. Many of them use ambiguous terms like "X lock" which seems to predate WiredTiger or the introduction of intent locks. Some staleness I've found:
|
| Comments |
| Comment by Matt Kneiser [ 06/Sep/22 ] |
|
First review of comments, raise a separate ticket for functionality. |