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

Create GC code for disassociated fact paths/values

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 2.3.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      PuppetDB 2015-02-25, PuppetDB 2015-03-11, PuppetDB 2015-03-25, PuppetDB 2015-04-08

      Description

      Although we currently remove disassociated fact paths/values "as we go", it's possible, if there are two concurrent transactions that each are pointing to the same fact path and value and they are simultaneously changing to a different value, their original value could be left behind. This process would clean those up. This seems to be pretty rare that it happens, so the number of fact values left behind is pretty low. These extra values don't actually cause problems (with the new table structure created in PDB-1224), but are just extra rows that will never be surfaced to the user.

      Care needs to be taken on the complexity of this query, how often it runs, how many records it would actually delete and the impact to the running system.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  rob.browning Rob Browning
                  Reporter:
                  ryan.senior Ryan Senior
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: