Jira (PDB-156) Handle large catalog sizes gracefully

2 views
Skip to first unread message

Kenneth Barber (JIRA)

unread,
Nov 18, 2015, 6:08:02 AM11/18/15
to puppe...@googlegroups.com
Kenneth Barber updated an issue
 
PuppetDB / New Feature PDB-156
Handle large catalog sizes gracefully
Change By: Kenneth Barber
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.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

Kenneth Barber (JIRA)

unread,
Nov 18, 2015, 6:41:08 AM11/18/15
to puppe...@googlegroups.com
Kenneth Barber updated an issue
Change By: Kenneth Barber
Sprint: PuppetDB 2015-12-02

Ryan Senior (JIRA)

unread,
Nov 18, 2015, 10:13:16 AM11/18/15
to puppe...@googlegroups.com
Ryan Senior updated an issue
Change By: Ryan Senior
Story Points: 8 3

Ryan Senior (JIRA)

unread,
Nov 18, 2015, 10:13:19 AM11/18/15
to puppe...@googlegroups.com
Ryan Senior commented on New Feature PDB-156
 
Re: Handle large catalog sizes gracefully

Eventually we want to support arbitrarily large catalogs, but that will be a significant change. Changing this ticket to fail fast on catalogs that are too large.

Kenneth Barber (JIRA)

unread,
Nov 18, 2015, 10:49:36 AM11/18/15
to puppe...@googlegroups.com
Kenneth Barber updated an issue
 
Change By: Kenneth Barber
Fix Version/s: PDB 4.0.0

Kurt Wall (JIRA)

unread,
Nov 20, 2015, 3:13:04 AM11/20/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Status: Reviewed

Kurt Wall (JIRA)

unread,
Nov 20, 2015, 3:14:02 AM11/20/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Risk Assessment: High

Kurt Wall (JIRA)

unread,
Nov 20, 2015, 3:14:04 AM11/20/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Risk Severity: High

Kurt Wall (JIRA)

unread,
Nov 20, 2015, 3:15:02 AM11/20/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Risk Probability: Medium

Kurt Wall (JIRA)

unread,
Nov 20, 2015, 3:16:05 AM11/20/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Risk Assessment Reason: Data loss (if not recovered from journal) and/or downtime

Ryan Senior (JIRA)

unread,
Nov 23, 2015, 11:13:04 AM11/23/15
to puppe...@googlegroups.com
Ryan Senior assigned an issue to Ryan Senior
Change By: Ryan Senior
Assignee: Ryan Senior

Susan McNerney (JIRA)

unread,
Dec 2, 2015, 11:52:16 AM12/2/15
to puppe...@googlegroups.com
Susan McNerney updated an issue
Change By: Susan McNerney
Sprint: PuppetDB 2015-12-02 , PuppetDB 2015-12-16

Kenneth Barber (JIRA)

unread,
Dec 10, 2015, 5:51:05 PM12/10/15
to puppe...@googlegroups.com
Kenneth Barber updated an issue
Change By: Kenneth Barber
Fix Version/s: PDB 4.0.0
Fix Version/s: PDB 3.2.x

Claudia Petty (Jira)

unread,
Jun 21, 2023, 10:56:05 AM6/21/23
to puppe...@googlegroups.com
Claudia Petty updated an issue
Change By: Claudia Petty
Labels: new-feature redmine
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages