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] [Comment Edited] (CASSANDRA-8113) Gossip should ignore generation numbers too far in the future
Date Fri, 17 Oct 2014 18:12:34 GMT

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

Brandon Williams edited comment on CASSANDRA-8113 at 10/17/14 6:12 PM:
-----------------------------------------------------------------------

To expound, we load saved endpoints with a generation of zero so it can be overridden on the
first gossip round.  Trivial patch attached for posterity; in testing now.


was (Author: brandon.williams):
Trivial patch attached for posterity; in testing now.

> 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, 8133-fix.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)

Mime
View raw message