cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8224) Checksum Gossip state
Date Tue, 07 Jul 2015 23:12:11 GMT

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

sankalp kohli updated CASSANDRA-8224:
-------------------------------------
    Attachment: incomplete_trunk_8224.diff

I am attaching this patch to give a sense of what this will do. The patch is not complete
as it does not handle that other nodes can alter the state of other nodes when we call remove,
etc. 

> Checksum Gossip state
> ---------------------
>
>                 Key: CASSANDRA-8224
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8224
>             Project: Cassandra
>          Issue Type: Improvement
>            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
(v6.3.4#6332)

Mime
View raw message