Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38698

Forgot to setOldestTimestamp when crash recovery in MongoDB 4.0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Duplicate
    • Affects Version/s: 4.0.0
    • Fix Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Operating System:
      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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36495 Cache pressure issues during recovery oplog application

          • Major - P3 - Major loss of function.
          • Open

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: