Forgot to setOldestTimestamp when crash recovery in MongoDB 4.0

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Critical - P2
    • None
    • Affects Version/s: 4.0.0
    • Component/s: Storage
    • None
    • ALL
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned
            Reporter:
            hellocode
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: