The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Feature #18881

Handle large catalog sizes gracefully

Added by Ken Barber over 3 years ago. Updated over 2 years ago.

Status:AcceptedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Keywords: Affected PuppetDB version:1.1.0

We've Moved!

Ticket tracking is now hosted in JIRA:

This ticket is now tracked at:


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 catalog receive size at the earlier HTTP stage (initially), or something more heuristic (long term).

Related issues

Related to PuppetDB - Bug #18804: Terrible exported resources performance Closed


#1 Updated by Ken Barber over 3 years ago

See linked issue #18804 for an example of how wrong this can go without some earlier checks.

#2 Updated by Ken Barber over 3 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 1.2.0
  • Affected PuppetDB version set to 1.1.0

#3 Updated by Ken Barber about 3 years ago

  • Target version deleted (1.2.0)

#4 Updated by Charlie Sharpsteen over 2 years ago

Redmine Issue #18881 has been migrated to JIRA:

Also available in: Atom PDF