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

Cache pressure issues during oplog replay in initial sync

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Replication
    • ALL

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: