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

Fix incorrect selection of stale-nodes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 4.0.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      2

      Description

      Currently, the stale-nodes computation will mark a node as stale if any relevant producer_timestamp is older than the node-ttl, when it ought to be checking whether the most recent timestamp is older.

      In theory, this could cause nodes to be expired prematurely, though we currently believe that as a practical matter, it's unlikely to happen in current deployments.

        Attachments

          Issue Links

          blocks

          Improvement - An improvement or enhancement to an existing feature or task. PDB-2576 Consider expiring multiple nodes in a single sql command

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

            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