[jira] [Updated] (CASSANDRA-12062) Prevent key invalidation if there's no key to invalidate

["Robert Stupp (JIRA)" <ji...@apache.org>]

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

Robert Stupp updated CASSANDRA-12062:
-------------------------------------
    Fix Version/s: 3.x
           Status: Patch Available  (was: Open)

Patch available (just started CI)
||trunk|[branch|https://github.com/apache/cassandra/compare/trunk...snazy:12062-invalidate-opts-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-12062-invalidate-opts-trunk-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-12062-invalidate-opts-trunk-dtest/lastSuccessfulBuild/]


> Prevent key invalidation if there's no key to invalidate
> --------------------------------------------------------
>
>                 Key: CASSANDRA-12062
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12062
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>            Priority: Minor
>             Fix For: 3.x
>
>
> In {{SSTableRewriter}} we currently assume that there are keys to be invalidated in the key cache. That's not always true - especially if a bunch of tiny sstables have been generated.
> Patch saves one {{synchronized}} and a few objects if that's the case.
> Just a small optimisation, but maybe worth to include.



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