During the 1.6.0 development cycle, we introduced an improvement to address
KUDU-2048 in 1e4db3148a1cb4e340aa96edaea85c733cfdbf5a that uses heuristics to decide whether it is safe to evict a failed replica or not. That patch appears to have a bug wherein the leader checks against the last time it communicated with itself, which is nonsensical. The issue is that the field it checks against is never updated for the local node.
We're currently investigating this issue and working on a fix.