[CASSANDRA-12217] Assassinate should use the current timestamp for the generation instead of incrementing

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 2.1.x
• Severity: Normal
• Assignee: Unassigned
• Reporter: Brandon Williams
• Created: 15/Jul/16 20:33
• Updated: 16/Apr/19 09:30

Description

In CASSANDRA-8113 we made gossip ignore generations more than a year in the future. While that is good, what can happen is this: you errantly have a machine start with a clock at, say, epoch+1, making the generation 1. Now, you're kind of stuck, because all other nodes will ignore you until you get up to now - 1 year, which from 1970 will take a lot of assassinates since it only increments the generation. Instead, I propose we use the assassinating node's timestamp as the generation, so that we have a way out of this aside from discarding the IP address for 3 days.