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

Handle resource event purges in one pass when possible

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.12.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      HA
    • Story Points:
      2
    • Release Notes:
      Enhancement
    • Release Notes Summary:
      PuppetDB now unifies report and resource event clean up during a full garbage collection, instead of handling each in a separate transaction. This ensures it only waits on the exclusive lock to drop relevant event partitions once.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Previously during a full gc, we'd gc reports (and the associated events), then we'd gc events (again). Instead, handle all the events during the report gc by adjusting the report gc to consider both the report ttl and the events ttl. Then in cases where we know we just ran the report gc, don't run the event gc.

      This will ensure we only wait on the exclusive lock to drop any
      relevant event partitons once during a full gc.

       

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support