[PDB-2617] Fix incorrect selection of stale-nodes Created: 2016/04/08 Updated: 2017/03/15 Resolved: 2016/04/21
|Fix Version/s:||PDB 4.0.2|
|Reporter:||Rob Browning||Assignee:||Rob Browning|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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.