[PDB-2617] Fix incorrect selection of stale-nodes Created: 2016/04/08  Updated: 2017/03/15  Resolved: 2016/04/21

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 4.0.2

Type: Bug Priority: Normal
Reporter: Rob Browning Assignee: Rob Browning
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
blocks PDB-2576 Consider expiring multiple nodes in a... Closed
Story Points: 2


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.

Generated at Wed Apr 01 14:00:51 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.