The impact is it'll get massively bigger with very little performance benefit, if any.
You can't get 0 because it's a probabilistic data structure. It tells you either: your data is definitely not here your data has a pretty decent chance of being here but never "it's here for sure" https://en.wikipedia.org/wiki/Bloom_filter On Wed, May 18, 2016 at 11:04 AM sai krishnam raju potturi < pskraj...@gmail.com> wrote: > hi Adarsh; > were there any drawbacks to setting the bloom_filter_fp_chance to the > default value? > > thanks > Sai > > On Wed, May 18, 2016 at 2:21 AM, Adarsh Kumar <adarsh0...@gmail.com> > wrote: > >> Hi, >> >> What is the impact of setting bloom_filter_fp_chance < 0.01. >> >> During performance tuning I was trying to tune bloom_filter_fp_chance and >> have following questions: >> >> 1). Why bloom_filter_fp_chance = 0 is not allowed. ( >> https://issues.apache.org/jira/browse/CASSANDRA-5013) >> 2). What is the maximum/recommended value of bloom_filter_fp_chance (if >> we do not have any limitation for bloom filter size). >> >> NOTE: We are using default SizeTieredCompactionStrategy on >> cassandra 2.1.8.621 >> >> Thanks in advance..:) >> >> Adarsh Kumar >> > >
