Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-2420

Sync core retains the local query result seq head

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.14.0, PDB 7.1.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      HA
    • Story Points:
      5
    • Sprint:
      HA 2021-01-27, HA 2021-02-10
    • Release Notes:
      Enhancement
    • Release Notes Summary:
      Hide
      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.
      Show
      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.

      Description

      Will have to change the api of query-fn to fix this; probably make it pass a thunk to the callback.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rob.browning Rob Browning
              Reporter:
              russell.mull Russell Mull
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support