You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 05:58:01 UTC

[jira] [Updated] (CASSANDRA-8224) Checksum Gossip state

     [ https://issues.apache.org/jira/browse/CASSANDRA-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

C. Scott Andreas updated CASSANDRA-8224:
----------------------------------------
    Component/s: Distributed Metadata

> Checksum Gossip state
> ---------------------
>
>                 Key: CASSANDRA-8224
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8224
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Distributed Metadata
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Minor
>         Attachments: incomplete_trunk_8224.diff
>
>
>  We have seen that a single machine with bad memory can corrupt the gossip of other nodes and cause entire cluster to be affected. If we store and pass the checksum of the entire state, we can detect corruption. If a bad machine tries to bump the generation number or other things, it will be detected and ignored.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org