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

Cache pressure issues during oplog replay in initial sync

    XMLWordPrintable

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Replication
    • ALL

    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

      • slow initial sync due to resulting cache churn
      • growth of lookaside (cache overflow) table and corresponding file WiredTigerLAS.wt
      • in extreme cases cache-full hangs were observed. This was believed fixed with SERVER-33191, but we should be alert for new occurrences of this issue.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              bruce.lucas@mongodb.com Bruce Lucas
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated: