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

Omitted FTDC sections cause frequent schema changes that limit FTDC retention

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 4.4.3, 5.0.0-rc0
    • None
    • None
    • Server Security
    • ALL
    • v5.0, v4.4
    • Execution Team 2021-10-04

    Description

      SERVER-30888 introduces the possibility that FTDC might be missing serverStatus.wiredTiger, serverStatus.oplog, and/or local.oplog.rs.stats sections. SERVER-48221 may have introduced a similar issue for the serverStatus.oplogTruncation and serverStatus.encryptionAtRest secitions. There might be other similar potentially omitted sections that I didn't find.

      This can cause frequent schema changes that reduce FTDC compression efficiency and limit retention. For example, in one deployment FTDC retention was reduced to less than 2 days, compared to a typical retention of closer to a week. The missing data can also cause us to miss important events in FTDC.

      It looks to me like the primary issue might be that we're using an extremely short timeout for acquiring the locks needed for collecting these sections, so it might be sufficient to increase the timeout to a substantial fraction of a second, although that needs verification.

      Attachments

        Activity

          People

            backlog-server-security Backlog - Security Team
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

              Created:
              Updated: