[
https://issues.apache.org/jira/browse/CASSANDRA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-3497:
--------------------------------------
Attachment: CASSANDRA-1.0-3497.txt
I added 2 new Bloom Filter related options to CFMetadata.
- filter_enabled
if set to false, SSTableReader uses EMPTY bloom filter. Default to true.
- fp_ratio
if the value is greater than 0, SSTableReader adjusts Bloom Filter based on
FP ratio and uses it. Default to 0.
BloomFilter is created and saved as usual, but when opening SSTableReader, you
got the one based on the CF setting.
One thing to note is that the change is effective when next time SSTableReader
is opened, so you need to restart node or compact/scrub sstable for existing
sstables.
> BloomFilter FP ratio should be configurable or size-restricted some other way
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-3497
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3497
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Brandon Williams
> Assignee: Yuki Morishita
> Priority: Minor
> Fix For: 1.0.7
>
> Attachments: CASSANDRA-1.0-3497.txt
>
>
> When you have a live dc and purely analytical dc, in many situations you can
> have less nodes on the analytical side, but end up getting restricted by
> having the BloomFilters in-memory, even though you have absolutely no use for
> them. It would be nice if you could reduce this memory requirement by tuning
> the desired FP ratio, or even just disabling them altogether.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
