[
https://issues.apache.org/jira/browse/CASSANDRA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174392#comment-13174392
]
Brandon Williams commented on CASSANDRA-3497:
---------------------------------------------
bq. Maybe easiest fix is to have node-wide setting for fp ratio in
cassandra.yaml (w/ jmx interface exposed) and have different values for each
datacenter?
Yes, I think that's good enough for the multi-datacenter scenario, however as
Radim mentioned we also have a good use case for a per-CF threshold. We could
do both, and then use whichever value is the lower, the one in the CF schema or
the one in the node's yaml.
> 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
>
>
> 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
