[SERVER-24376] Capped deletion in WT should stop using a side transaction Created: 02/Jun/16 Updated: 06/Dec/22 Resolved: 01/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
The side transaction is from when we thought concurrent writes to capped collections made sense. Now that we are single-threading all capped inserts, we should make the deletion be part of the inserting transaction, as it is in MMAPv1. This will fix a lot of odd behaviors around rollback or small caps. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 01/Jun/18 ] |
|
This code has changed and there are no more side transactions. |