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

PDB performance issues with large structured facts

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PDB 4.4.1
    • Fix Version/s: PDB 5.2.0
    • Component/s: PuppetDB
    • Labels:
      None
    • Template:
    • Sprint:
      Hopper/Triage, Data Platform 2017-10-18
    • Method Found:
      Customer Feedback
    • CS Priority:
      Critical
    • CS Frequency:
      4 - 50-90% of Customers
    • CS Severity:
      4 - Major
    • CS Business Value:
      5 - $$$$$$
    • CS Impact:
      Hide
      This is a very common and troubleshooting it has consumed a huge amount of support time. The workaround is to stop sending large structured facts which in some cases impacts their use of puppet.

      In one example a custom structured fact collected rpm data which they were using in their code somehow so turning it off wasn't really a workaround but a reduction in functionality.

      This can be very common on Solaris where there is a mount per user. A 20-30KB structured fact can be easily reached on solaris and cause this issue.
      Show
      This is a very common and troubleshooting it has consumed a huge amount of support time. The workaround is to stop sending large structured facts which in some cases impacts their use of puppet. In one example a custom structured fact collected rpm data which they were using in their code somehow so turning it off wasn't really a workaround but a reduction in functionality. This can be very common on Solaris where there is a mount per user. A 20-30KB structured fact can be easily reached on solaris and cause this issue.
    • Release Notes:
      Not Needed

      Description

      As outlined in PDB-2631, PuppetDB encounters severe performance degradation in the presence of large structured facts. In support, we have seen this impact with mountpoint or partitions facts of only 20-30 KiB, which is not terribly uncommon. As noted in that ticket, the expectation is that PDB will be able to handle anything Facter might throw at it.

      This issue was resolved in PDB-3249, but the fix was removed by PDB-3611. We need a solution that will allow large structured facts to be stored in PDB without causing causing query performance issues.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                adam.bottchen Adam Bottchen
              • Votes:
                2 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support