Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync

23 views
Skip to first unread message

Nick Walker (JIRA)

unread,
Nov 7, 2017, 11:29:03 AM11/7/17
to puppe...@googlegroups.com
Nick Walker created an issue
 
PuppetDB / Improvement PDB-3751
PDB Sync should allow a separate setting for the maximum amount of reports to sync
Issue Type: Improvement Improvement
Assignee: Unassigned
Created: 2017/11/07 8:28 AM
Priority: Normal Normal
Reporter: Nick Walker

The Problem

By default, PDB sync will try to sync all reports in the database with the other PuppetDB. Syncing all of the reports in the database is generally not valuable and syncing a smaller portion and then growing the new sync node as new reports come in would likely work great for 90% of users.

In this case, you could set the sync-report-ttl to say 1d while leaving report-ttl at 14d. When setting up a new sync node you'd only sync 1d of reports and over the next 13 days the new reports coming in would bring the sync node up to the 14d of report-ttl.

This also allows for sync to go down for multiple days and then come back up relatively quickly depending on how you decide to configure these settings.

Having this as a configurable setting provides a release valve when you're trying to get sync working and you don't want to wait for 14 days of reports to sync. You just want sync working now and you don't care about the reports syncing all the way back in time.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Atlassian logo

Owen Rodabaugh (JIRA)

unread,
Nov 9, 2017, 7:09:04 PM11/9/17
to puppe...@googlegroups.com
Owen Rodabaugh updated an issue
Change By: Owen Rodabaugh
CS Priority: Needs Priority Normal
CS Impact: Customers with a large number of reports, or who store more than the default days of reports will take a long time to sync those reports if they lose connectivity between PDB nodes. This would get their sync running again much faster.

This is analogous to situations where customers run out of disk space on the postgres node. They can truncate the reports table to get running again if they don't need old reports.
CS Severity: 3 - Serious
CS Business Value: 4 - $$$$$
CS Frequency: 2 - 5-25% of Customers

Austin Blatt (JIRA)

unread,
Nov 25, 2019, 1:42:05 PM11/25/19
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Team: HA
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Nick Burgan (JIRA)

unread,
Jan 15, 2020, 2:29:04 PM1/15/20
to puppe...@googlegroups.com

Nick Burgan (JIRA)

unread,
Jan 15, 2020, 2:29:04 PM1/15/20
to puppe...@googlegroups.com

Nick Burgan (JIRA)

unread,
Jan 15, 2020, 2:29:04 PM1/15/20
to puppe...@googlegroups.com

Nick Burgan (JIRA)

unread,
Jan 29, 2020, 2:04:05 PM1/29/20
to puppe...@googlegroups.com
Nick Burgan updated an issue
Change By: Nick Burgan
Sprint: HA Team 2020-01-29 , HA Team 2020-02-12

Melissa Amos (JIRA)

unread,
Feb 7, 2020, 1:42:05 PM2/7/20
to puppe...@googlegroups.com

Nick Burgan (JIRA)

unread,
Feb 12, 2020, 2:05:06 PM2/12/20
to puppe...@googlegroups.com
Nick Burgan updated an issue
Change By: Nick Burgan
Sprint: HA Team 2020-01-29, HA Team 2020-02-12 , HA Team 2020-02-26

Austin Blatt (JIRA)

unread,
Feb 20, 2020, 6:08:17 PM2/20/20
to puppe...@googlegroups.com

Austin Blatt (Jira)

unread,
Mar 5, 2020, 8:40:03 PM3/5/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Fix Version/s: PDB 5.2.13
Fix Version/s: PDB 6.9.0
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Austin Blatt (Jira)

unread,
Mar 5, 2020, 8:41:03 PM3/5/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Fix Version/s: PDB 6.10.0
Fix Version/s: PDB 6.9.1

Austin Blatt (Jira)

unread,
Mar 5, 2020, 8:41:03 PM3/5/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Fix Version/s: PDB 6.9.0
Fix Version/s: PDB 6.10.0

Austin Blatt (Jira)

unread,
Mar 5, 2020, 8:50:03 PM3/5/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Release Notes: Enhancement New Feature
Release Notes Summary: Adds the initial-report-threshold config option to the sync settings. On startup, PuppetDB will only sync reports newer than the threshold. Older reports will still be transferred on subsequent periodic syncs.
Reply all
Reply to author
Forward
0 new messages