[SERVER-38698] Forgot to setOldestTimestamp when crash recovery in MongoDB 4.0 Created: 19/Dec/18 Updated: 19/Dec/18 Resolved: 19/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | hellocode | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In ReplicationRecovery::_applyToEndOfOplog, you forgot to call StorageEngine::setOldestTimestamp to release WiredTiger cache, it may lead to stressful cache pressure when crash recovery. Neither ApplyBatchFinalizer nor ReplicationCoordinatorImpl::setMyLastAppliedOpTimeForward be called. I have described details in google groups Please let me know if any progress. |
| Comments |
| Comment by Eric Milkie [ 19/Dec/18 ] |
|
Thank you for filing this ticket. We have a SERVER ticket tracking this issue: |