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 Tue, 14 Oct 2014 18:20:35 GMT

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

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

Also there's no real contract for how often you can update your gossip state if you want to,
so we could have an accidental loop blow the version up and then run into further problems
because now it's being ignored.

> 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
>         Attachments: 8113-v1.txt, 8113-v2.txt, 8113-v3.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