[
https://issues.apache.org/jira/browse/CASSANDRA-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reopened CASSANDRA-8113:
-----------------------------------------
It turns out we probably also need to ignore this check when the localgen is
zero:
{noformat}
WARN [GossipStage:1] 2014-10-17 05:51:42,554 Gossiper.java:993 - received an
invalid gossip generation for peer /127.0.0.3; local
generation = 0, received generation = 1413524483.
{noformat}
> Gossip should ignore generation numbers too far in the future
> -------------------------------------------------------------
>
> Key: CASSANDRA-8113
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8113
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Richard Low
> Assignee: Jason Brown
> Fix For: 2.1.1
>
> Attachments: 8113-v1.txt, 8113-v2.txt, 8113-v3.txt, 8113-v4.txt
>
>
> If a node sends corrupted gossip, it could set the generation numbers for
> other nodes to arbitrarily large values. This is dangerous since one bad node
> (e.g. with bad memory) could in theory bring down the cluster. Nodes should
> refuse to accept generation numbers that are too far in the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
