Jira (PDB-3742) Sync should skip records that are already present in the command queue

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen created an issue

PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue Issue Type: Improvement Affects Versions: PDB 5.1.3 Assignee: Unassigned Created: 2017/11/01 10:07 AM Priority: Normal Reporter: Charlie Sharpsteen PuppetDB sync compares the contents of two databases and transfers over any data that isn't present in the local database. If a large amount of data is transferred, a large command queue will be created which has to be worked off. This can result in several sync cycles transferring the same data before the first copy reaches the front of the command queue and is inserted into the database. PuppetDB sync should list the IDs of records in the queue at the beginning of sync and skip transferring any remote records that are included in the list. Add Comment

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

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen updated an issue

PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue

Change By: Charlie Sharpsteen CS Priority: Needs Priority

Add Comment

[Owen Rodabaugh (JIRA)]

Owen Rodabaugh updated an issue

PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue

Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: This can lead to long sync times for customers which have a lot of data to sync. In those cases this causes the sync process to consume many more resource than it should. Such as database connections, CPU usage, network traffic, all to process sync data that is already sitting in the command queue waiting to get into the database. CS Severity: 3 - Serious CS Business Value: 4 - $$$$$ CS Frequency: 2 - 5-25% of Customers

Add Comment

[Zachary Kent (JIRA)]

Zachary Kent assigned an issue to Zachary Kent

PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue

Change By: Zachary Kent Assignee: Zachary Kent

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Nirupama Mantha (JIRA)]

Nirupama Mantha commented on PDB-3742

Re: Sync should skip records that are already present in the command queue Zachary Kent Can you update release notes for this?

Add Comment

[Zachary Kent (JIRA)]

Zachary Kent updated an issue

PuppetDB / PDB-3742

Sync should skip records that are already present in the command queue

Change By: Zachary Kent Release Notes Summary: Allow PupppetDB to take already enqueued commands into account when deciding which records need to by pulled from a remote PuppetDB during HA Sync. This fixes an issue where duplicate commands could be added to the command queue during sync, which could result in extra work and more downtime before the PuppetDB doing the sync could respond to new commands.

Add Comment

[Zachary Kent (JIRA)]

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue

Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Fix Version/s: PDB 5.2.9

Add Comment