Details
-
Bug
-
Status: Closed
-
Critical - P2
-
Resolution: Duplicate
-
4.0.0
-
None
-
None
-
ALL
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.
Attachments
Issue Links
- duplicates
-
SERVER-36495 Cache pressure issues during recovery oplog application
-
- Closed
-