cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8113) Gossip should ignore generation numbers too far in the future
Date Mon, 13 Oct 2014 20:58:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169956#comment-14169956
] 

Brandon Williams commented on CASSANDRA-8113:
---------------------------------------------

bq. What if your local clock is borked?

Then you have bigger problems ;)

bq. Perhaps, a remote node's last version + an approximation of the number of updates in a
year (86400 * 365) = 31,536,000. 

Sounds reasonable to me.

> 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
>
> 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)

Mime
View raw message