cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-8434) L0 should have a separate configurable bloom filter false positive ratio
Date Fri, 22 Jul 2016 16:30:21 GMT

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

Jonathan Ellis resolved CASSANDRA-8434.
---------------------------------------
    Resolution: Later

OTOH automatically bumping up BF granularity for L0 when it's in an overload situation could
cause other kinds of badness, e.g. unexpected memory pressure.  Not sure if this is worth
the cost/benefit to solve robustly, so closing as Later.

> L0 should have a separate configurable bloom filter false positive ratio
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8434
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8434
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benedict
>             Fix For: 2.1.x
>
>
> In follow up to CASSANDRA-5371. We now perform size-tiered file selection for compaction
if L0 gets too far behind, however as far as I can tell we stick with the CF configured false
positive ratio, likely inflating substantially the number of files we visit on average until
L0 is cleaned up. Having a a different bf fp for L0 would solve this problem without introducing
any significant burden when L0 is not overloaded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message