[SERVER-36496] Cache pressure issues during oplog replay in initial sync Created: 07/Aug/18 Updated: 02/Oct/23 Resolved: 02/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
During oplog replay in initial sync we don't advance the oldest timestamp. This can pin a lot of data in the cache. Resulting symptoms include
|
| Comments |
| Comment by Lingzhi Deng [ 02/Oct/23 ] |
|
We think this problem goes away with WT history store. |