The current implementation of clusterNodeCleanupFailureReports walks the entire fail reports in the list on every invocation and performs a listDelNode() for each expired or non‑voting entry. When a cluster node has accumulated hundreds or thousands of failure reports, this function becomes a CPU hotspot.

(The above result was observed during a 2,000‑node cluster failover scenario)

Current behavior:

• Where N is the number of failure reports, O(N) scan on every call, regardless of how many reports are actually expired.

Improvement ideas:

• Use a priority queue with expiration time, so expired nodes can be removed in O(RlogN) rather than scanned in full. (R is # of actually expired reports)
• Use lazy deletion instead of removing them on every call
• Use early exit when meeting quorum