[jira] [Commented] (CASSANDRA-10341) Streaming does not guarantee cache invalidation

["Paulo Motta (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876682#comment-14876682 ] 

Paulo Motta commented on CASSANDRA-10341:
-----------------------------------------

I thought of iterating over all the received {{SSTableReader}} keys on {{StreamReceiveTask.OnCompletionRunnable}} and invalidate the keys before adding them to {{ColumnFamilyStore}}. Is this a valid approach or do you think there is a more efficient way of doing this, [~benedict]? Do we want to perform the cache invalidation and addition of sstables to {{ColumnFamilyStore}} atomically, or is it acceptable to invalidate just before adding?

> Streaming does not guarantee cache invalidation
> -----------------------------------------------
>
>                 Key: CASSANDRA-10341
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10341
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Paulo Motta
>
> Looking at the code, we attempt to invalidate the row cache for any rows we receive via streaming, however we invalidate them immediately, before the new data is available. So, if it is requested (which is likely if it is "hot") in the interval, it will be re-cached and not invalidated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)