natas_hw
/
cassandra
mirror of https://github.com/apache/cassandra
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'cassandra-2.0' into cassandra-2.1.0

This commit is contained in:
Jonathan Ellis 2014-07-16 16:17:44 -05:00
parent 6b988fddd0 93c27549a3
commit 545e2e1cba
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
conf/cassandra.yaml
View File

@ -488,13 +488,15 @@ auto_snapshot: true
tombstone_warn_threshold: 1000 tombstone_warn_threshold: 1000
tombstone_failure_threshold: 100000 tombstone_failure_threshold: 100000
# Add column indexes to a row after its contents reach this size. # Granularity of the collation index of rows within a partition.
# Increase if your column values are large, or if you have a very large # Increase if your rows are large, or if you have a very large
# number of columns. The competing causes are, Cassandra has to # number of rows per partition. The competing goals are these:
# deserialize this much of the row to read a single column, so you want # 1) a smaller granularity means more index entries are generated
# it to be small - at least if you do many partial-row reads - but all # and looking up rows withing the partition by collation column
# the index data is read for each access, so you don't want to generate # is faster
# that wastefully either. # 2) but, Cassandra will keep the collation index in memory for hot
# rows (as part of the key cache), so a larger granularity means
# you can cache more hot rows
column_index_size_in_kb: 64 column_index_size_in_kb: 64