cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1878) Minimize Key Cache Invalidation by Compaction
Date Mon, 20 Dec 2010 04:51:02 GMT

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

Hudson commented on CASSANDRA-1878:
-----------------------------------

Integrated in Cassandra-0.6 #29 (See [https://hudson.apache.org/hudson/job/Cassandra-0.6/29/])
    Re-cache hotkeys post-compaction without hitting disk
patch by jbellis; reviewed by tjake for CASSANDRA-1878


> Minimize Key Cache Invalidation by Compaction
> ---------------------------------------------
>
>                 Key: CASSANDRA-1878
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1878
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Jonathan Ellis
>             Fix For: 0.6.9, 0.7.0
>
>         Attachments: 1878.txt, 1878_v2.txt
>
>
> Currently, compactions invalidate key cache entries that pointed to the SSTables that
were compacted.  This results in a sudden increase in the number of seeks necessary for reads
immediately after compaction.  When writing out a new SSTable after a compaction, it seems
like it should be possible to store a list of keys that are currently cached but would be
invalidated along with their new position in the new SSTable.  Matt Dennis also seems to think
this would be relatively easy to do.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message