Jira (PDB-2420) Sync core retains the local query result seq head

[Russell Mull (JIRA)]

Russell Mull created an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head Issue Type: Bug Assignee: Unassigned Created: 2016/02/10 3:59 PM Priority: Normal Reporter: Russell Mull Will have to change the api of query-fn to fix this; probably make it pass a thunk to the callback. Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Austin Blatt (Jira)]

Austin Blatt assigned an issue to Rob Browning

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Austin Blatt Assignee: Rob Browning

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Rob Browning Story Points: 5

Add Comment

[Zachary Kent (Jira)]

Zachary Kent updated an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Zachary Kent Epic Link: PDB- 1711 4969

Add Comment

[Zachary Kent (Jira)]

Zachary Kent updated an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Zachary Kent Sprint: HA 2021-01-27

Add Comment

[Eric Thompson (Jira)]

Eric Thompson updated an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Eric Thompson Sprint: HA 2021-01-27 , HA 2021-02-10

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Austin Blatt Fix Version/s: PDB 7.1.0 Fix Version/s: PDB 6.14.0

Add Comment

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-2420 Sync core retains the local query result seq head

Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: PuppetDB should synchronize with another instance more efficiently now.  Previously it would synchronize each entity (factsets, reports, etc.) incrementally, holding open PostgreSQL queries/transactions throughout the entire process, which could take a long time.  Those transactions could substantially harm database performance, increase table fragmentation, and if entangled with something like pglogical, increase transient storage requirements (by blocking WAL log reclaimaton).  Now instead, the queries should completed up-front, as quickly as possible. Team: HA

Add Comment