[
https://issues.apache.org/jira/browse/CASSANDRA-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617625#comment-14617625
]
sankalp kohli commented on CASSANDRA-8224:
------------------------------------------
We can change the implementation to log when checksum does not match instead of
ignoring the gossip. This way we can find the bad host.
> 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)
