Poor FTDC compression due to apparent schema change observed on 7.3.0-alpha1

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0, 7.3.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v7.3
    • Execution Team 2024-02-05
    • 100
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Environment

      • MongoDB 7.3.0-alpha1
      • Single node replica set
      • macOS

      Happened to observe that a new 10MB FTDC file was being rolled every 8 minutes instead of the more typical 4-8 hours.

      Based on some internal discussion this is thought to be caused by frequent schema changes brought on by a separate memory optimization.

      This is apparently trivially reproducible on linux. Example logs from a linux repro:

      "full-time diagnostic data capture schema change: field name change","attr":{"from":"block-manager","to":"cursor"}}
      "full-time diagnostic data capture schema change: field name change","attr":{"from":"cursor","to":"block-cache"}}
      

              Assignee:
              Henrik Edin
              Reporter:
              John Morales (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: