cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3497) BloomFilter FP ratio should be configurable or size-restricted some other way
Date Wed, 21 Dec 2011 18:29:31 GMT

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

Yuki Morishita commented on CASSANDRA-3497:
-------------------------------------------

The problem is that currently strategy_options for NTS is thoroughly for replication setting,
for example {DC1:2, DC2:2}.
We can do like strategy_options={DC1:2, DC2:1, DC2:fp(0.5)} or strategy_options={DC1:2, DC2:1,fp(0.5)}
or something  preserving backward compatibility, but I think it's complicated.

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?
                
> 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

        

Mime
View raw message