[SERVER-50353] Background validation should periodically restart its storage transaction Created: 18/Aug/20 Updated: 29/Sep/20 Resolved: 22/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| 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, Execution Team 2020-10-05 | ||||||||
| Participants: | |||||||||
| Description |
|
In order to prevent cache pressure, background validation should periodically start a new storage transaction at the same read timestamp and then roll back its current storage transaction. This overlap of transactions should prevent WiredTiger from evicting data needed by the transactions, but the establishment of a new snapshot will allow eviction to move newly committed updates into the durable history store. |
| Comments |
| Comment by Eric Milkie [ 22/Sep/20 ] |
|
Committed as part of |