[
https://issues.apache.org/jira/browse/CASSANDRA-14590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-14590:
---------------------------------------
Fix Version/s: (was: 4.0.x)
4.x
> Size of fixed-width write values not verified from peers
> ---------------------------------------------------------
>
> Key: CASSANDRA-14590
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14590
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Streaming and Messaging
> Reporter: Benedict Elliott Smith
> Priority: Low
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> There are any number of reasons data arriving on a node might be corrupt in a
> manner that can ultimately pollute non-corrupt data. CASSANDRA-14568 is just
> one example. In this bug’s case, invalid clusterings were sent to a legacy
> version peer, which eventually sent them back to a latest version peer. In
> either case, verification of the size of the values arriving would have
> prevented the corruption spreading, or affecting whole-sstable operations
> containing the values.
>
> I propose verifying the fixed-width types arriving from peers, and also on
> serialization. The former permits rejecting the write with an exception, and
> preventing the write being ACK’d, or polluting memtables (thus maintaining
> update atomicity without affecting more records). The latter will be a
> guarantee that this corruption cannot make it to an sstable via any other
> route (e.g. a bug internal to the node)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
