cassandra-commits mailing list archives

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


Jason Brown commented on CASSANDRA-8113:

What happens when you have a network partition that lasts days (or a week or two)? The heartbeat
is updated, more or less, once a second. So the version of a given node can increment by ~86400
per day (minus a few for GC collection, thread scheduling, etc) . Depending on what you think
a "too far in the future" value is, if you set that high water mark too low, you will doom
the cluster to never converging, as well. If we want to consider a high water mark of difference
as a couple million, or so, that might be reasonable.

> Gossip should ignore generation numbers too far in the future
> -------------------------------------------------------------
>                 Key: CASSANDRA-8113
>                 URL:
>             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

View raw message