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

Avoid stalling ftdc when system is struggling

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • None
    • Diagnostics
    • ALL

    Description

      FTDC can stall for a few reasons when the system is struggling, but this is just when it might be most helpful. Reasons include

      • out of tickets
      • cache is full and ftdc thread gets used to do evictions - the ignore_cache_size session option (WT-2932) might help here

      We should arrange for FTDC not to get stalled by these conditions.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32876 Don't stall ftdc due to WT cache full

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32875 Don't stall ftdc due to running out of tickets

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-32226 oldest_timestamp should track the last applied time, during initial sync

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              mark.benvenuto@mongodb.com Mark Benvenuto
              bruce.lucas@mongodb.com Bruce Lucas
              Votes:
              34 Vote for this issue
              Watchers:
              26 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: