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

Clean up orphaned edges

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PDB 4.2.3, PDB 4.2.3.1, PDB 4.2.3.2, PDB 4.2.3.3, PDB 4.3.0, PDB 4.3.1, PDB 4.3.2, PDB 4.4.0
    • Fix Version/s: PDB 4.2.3.4, PDB 4.4.1, PDB 5.0.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Data Platform
    • Story Points:
      2
    • Sprint:
      Hopper/Triage, PuppetDB 2017-05-31
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      PuppetDB was leaving unused 'edge' records in the database. For most users this had very little impact, but they could pile up over time as nodes are purged if [node-purge-ttl](https://docs.puppet.com/puppetdb/4.4/configure.html#node-purge-ttl) is non-zero. The unused edges will now be removed on upgrade and continuously cleaned up when they are no longer needed.
      Show
      PuppetDB was leaving unused 'edge' records in the database. For most users this had very little impact, but they could pile up over time as nodes are purged if [node-purge-ttl]( https://docs.puppet.com/puppetdb/4.4/configure.html#node-purge-ttl ) is non-zero. The unused edges will now be removed on upgrade and continuously cleaned up when they are no longer needed.
    • QA Risk Assessment:
      Needs Assessment

      Description

      If this is what it looks like (not deleting edges when a node is purged), then we'll probably want to make sure to call delete-edges! during purge, and add a migration to handle existing orphans. We'll also want to add a test to make sure that the addition and deletion of a set of nodes leaves no trace (perhaps via dump, or via "all table" traversal).

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support