cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T. David Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8113) Gossip should ignore generation numbers too far in the future
Date Wed, 23 Dec 2015 16:38:46 GMT

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

T. David Hudson commented on CASSANDRA-8113:
--------------------------------------------

I'm seeing 3 nodes of a 4-node Cassandra 2.1.1 (upgraded from 2.Xs a while back) cluster reporting
ancient generations and refusing to accept a modern generation from the fourth.  Could the
generation check allow a timestamp far past the local generation but nevertheless reasonable
w.r.t. the current system clock?

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