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

Tyler Hobbs updated CASSANDRA-6379:
-----------------------------------

    Attachment: 6379-thrift-gen.txt
                6379.txt

6379.txt (and [branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-6379]) 
replaces {{index_interval}} with {{min_index_interval}} and 
{{max_index_interval}}.  When migrating, the existing {{index_interval}} value 
is used for {{min_index_interval}}.  I chose 2048 for the default 
{{max_index_interval}}; in practice, this limit should only be hit for 
infrequently-read SSTables when the index summary memory pool is very full.

If you want to test it out, I suggest setting logging to TRACE for 
o.a.c.io.sstable.IndexSummary manager, setting {{index_summary_capacity_in_mb}} 
to 1, and {{index_summary_resize_interval_in_minutes}} to 1.  After inserting a 
few million rows with stress, the index summary pool will hit capacity and some 
resizing will happen.  The JMX functions on IndexSummaryManager are also handy.


> Replace index_interval with min/max_index_interval
> --------------------------------------------------
>
>                 Key: CASSANDRA-6379
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6379
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>             Fix For: 2.1
>
>         Attachments: 6379-thrift-gen.txt, 6379.txt
>
>
> As a continuation of the work in CASSANDRA-5519, we want to replace the 
> {{index_interval}} attribute of tables with {{min_index_interval}} and 
> {{max_index_interval}}.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to