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

Handle large catalog sizes gracefully

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 3.2.3
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      3
    • Sprint:
      PuppetDB 2015-12-02, PuppetDB 2015-12-16

      Description

      If we get a large catalog, the JVM will crash with OOM errors if not sized correctly. This is not very elegant, and we need a much nicer way of dealing with this.

      We should have a way of dealing with this, either through a configurable option for maximum catalog receive size at the earlier HTTP stage (initially), or something more heuristic (long term). We should either way, not throw an OOM if we can avoid it.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  redmine.exporter redmine.exporter
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support