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

Cache-full hangs on 3.6

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.7, 4.0.1, 4.1.2
    • Affects Version/s: 3.6.2, 3.6.5
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Storage NYC 2018-07-16, Storage NYC 2018-07-30

      We have seen a couple of cases in the field where under heavy cache pressure a node can get stuck with the WT cache full. In the cases seen so far the cache pressure has been due to replica set lag, which causes the majority commit point to lag, creating cache pressure.

      So far we don't have a reproducer and don't have FTDC data covering the inception of the issue (SERVER-32876) so this ticket for now is a placeholder to gather information.

        1. metrics.2018-05-30T17-31-46Z-00000
          59 kB
        2. repro-10MBx2.sh
          1 kB
        3. stacks.txt
          65 kB
        4. stuck.png
          166 kB

            benety.goh@mongodb.com Benety Goh
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            1 Vote for this issue
            21 Start watching this issue