Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-2423

Limit initial sync to catalogs, factsets, and deactivate node commands

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • PuppetDB
    • HA
    • 2
    • HA Team 2020-01-29, HA Team 2020-02-12, HA Team 2020-02-26
    • Reviewed
    • Enhancement

    Description

      To limit start up time for PuppetDB replicas, we need to limit the amount of data that is transferred.

      Currently we sync

      • Catalogs
      • Factsets
      • Reports
      • Node deactivation
      • Catalog Inputs (for cd4pe)

      By far the two largest sets of data are reports and catalog inputs, so I think that initial sync should be limited to the following to ensure a somewhat fast startup time.

      • Catalogs
      • Factsets
      • Node deactivation

      The most commonly suggested modification to this list is to also sync only the latest reports. I haven't heard a reason to spend startup time syncing the latest report for a replica PuppetDB because all the time PDB spends in startup sync it is drifting out of alignment. If someone has a good reason that a replica PuppetDB should have the latest reports when it starts up, I would be happy to add that to the list of things to sync.

      Attachments

        Issue Links

          Activity

            People

              austin.blatt Austin Blatt
              russell.mull Russell Mull
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support