[CASSANDRA-640] Repair should never reuse a tree

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 0.5
• Severity: Normal
• Assignee: Stu Hood
• Reporter: Stu Hood

Authors

Stu Hood

• Created: 18/Dec/09 01:14
• Updated: 16/Apr/19 09:33
• Resolved: 19/Dec/09 08:06

Description

AEService currently 'caches' MerkleTrees that have been generated by the local node, and can respond to a request for a tree with a cached version. This means that despite possibly having performed a repair, the two nodes will still be holding cached trees, and can respond to one another with the cached version, resulting in redundant repairs.

Rather than a cache, the map of trees is intended to be a rendezvous point for two nodes to exchange relatively up-to-date trees. A map still might work, but other synchronization objects should be explored.