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

Presence of initialSyncStatus in replSetGetStatus consumes too much FTDC space

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 4.2.1
    • 4.2.8, 4.4.0-rc5, 4.7.0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Repl 2020-05-18

    Description

      SERVER-7019 turned on initialSyncStatus in replSetGetStatus by default, and that causes it to be included in FTDC. However this means that for a user with a very large number of collections there will be a very large number of keys and a lot of expensive schema changes in FTDC, using a very large amount of space and becoming unworkably large. This causes problems for consuming tools, and means that FTDC can roll over before initial sync completes.

      We should exclude the initialSyncStatus section from in replSetGetStatus FTDC.

      Attachments

        Issue Links

          Activity

            People

              samy.lanka@mongodb.com Samyukta Lanka
              bruce.lucas@mongodb.com Bruce Lucas
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: