[
https://issues.apache.org/jira/browse/CASSANDRA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855423#action_12855423
]
Jonathan Ellis commented on CASSANDRA-946:
------------------------------------------
getRangeSlice doesn't populate cache automatically, by design. You need to
call
ssTables_.getRowCache().put(key, cf);
for each row.
You need to pass null as the first argument to getRangeSlice, otherwise it will
only load a supercolumn with an empty name into the resultset. This is not
what you want.
Please read http://wiki.apache.org/cassandra/CodeStyle and follow the bracing
and exception-handling guidelines there.
When testing, use the JMX mbean to see if the cache has data loaded, then do
some queries to see if it's actually the *right* data.
> Add a configuration and implementation to populate the data into memory
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-946
> URL: https://issues.apache.org/jira/browse/CASSANDRA-946
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7
> Environment: Linux, Cassandra
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.7, 0.8
>
> Attachments: 946-Add_Config_v001.txt, 946-Add_Config_v002.txt,
> 946-Documentation_v002.txt, 946-Load_Data_v001.txt, 946-Load_Data_v002.txt
>
>
> Proactively load data into the memory when the node is started, there will be
> a configuration to enable this function and will be per Columnfamily. The
> requirement is to speed up the reads for data which can reside 100% of in the
> memory.... In addition to enabling the RowCache to 100% we can do this so as
> upgrades or any other means of restart will not clear the cache in the server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
