[SERVER-44969] Remove the mutex around WT compact calls Created: 05/Dec/19 Updated: 27/Oct/23 Resolved: 08/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Vishnu Kaushik |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng, newgrad | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2020-09-07, Execution Team 2020-09-21 | ||||||||
| Participants: | |||||||||
| Description |
|
A mutex was introduced around calling the WT compact cmd during the Background Validation project. Explore what operations might be able to share the mutex, and which need exclusive access. This would reduce contention in concurrency workloads executing compact cmds.
|
| Comments |
| Comment by Vishnu Kaushik [ 08/Sep/20 ] |
|
This is no longer an issue thanks to |
| Comment by Connie Chen [ 20/Jul/20 ] |
|
This is no longer necessary since we have removed checkpoint validation. Updated title to reflect what we think should be done now. |
| Comment by Louis Williams [ 05/Dec/19 ] |
|
The compact command would still need to conflict with checkpoints, correct? That's why the mutex was used in the first place. |