You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Burroughs (JIRA)" <ji...@apache.org> on 2011/06/21 21:55:47 UTC

[jira] [Issue Comment Edited] (CASSANDRA-1966) Option to control how many items are read on cache load

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

Chris Burroughs edited comment on CASSANDRA-1966 at 6/21/11 7:54 PM:
---------------------------------------------------------------------

- double --> int for thrift/avro
- -1 --> max int for special value (but it's still a special value)
- CLI support
- Schema migration should work now, only jmx changes worked with v1.

I think I got everything from http://wiki.apache.org/cassandra/ConfigurationNotes down, but admit that I'm nervous at the size of the patch.

Max int is slightly confusing in jconsole, but I don't have a strong opinion between that and -1.

      was (Author: cburroughs):
    - double --> int for thrift/avro
- -1 --> max int for special value (but it's still a special value)
- CLI support

I think I got everything from http://wiki.apache.org/cassandra/ConfigurationNotes down, but admit that I'm nervous at the size of the patch.

Max int is slightly confusing in jconsole, but I don't have a strong opinion between that and -1.
  
> Option to control how many items are read on cache load
> -------------------------------------------------------
>
>                 Key: CASSANDRA-1966
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1966
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>            Priority: Minor
>         Attachments: 1966-v1.txt, 1966-v2.txt
>
>
> CASSANDRA-1417 added an option to save the key and/or row cache keys which is cool.  However, for a row large cache it can take a long time to read all of the rows.  For example I have a 400,000 item row cache, and loading that on restart takes a little under an hour.
> In addition to configuring the size of the row cache, and how often it should be saved to disk, I propose an option to control how many items are loaded on startup (or alternately only saving n items out of the full row cache to begin with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira