You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Delaney Manders (JIRA)" <ji...@apache.org> on 2012/12/10 01:07:20 UTC

[jira] [Updated] (CASSANDRA-5047) Allow bloom_filter_fp_chance to be configured differently per data center

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

Delaney Manders updated CASSANDRA-5047:
---------------------------------------

    Issue Type: Wish  (was: New Feature)
    
> Allow bloom_filter_fp_chance to be configured differently per data center
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5047
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5047
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>    Affects Versions: 1.2.0 rc1
>            Reporter: Delaney Manders
>            Priority: Minor
>
> When using one data center for hadoop/analytics exclusively, one for serving high volume writes, and possibly even one for reads, the tuning requirements are dramatically different on the same column family.
> The biggest heap cost on a large dataset is the bloom_filter.  It would be great to be able to disable/tune it as a per-datacentre setting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira