A few more details: 1. bloom_filter_fp_chance is set to 0.01
2. I reviewed CASSANDRA-8413 (https://github.com/apache/cassandra/commit/23fd75f27c40462636f09920719b5dcbef5b8f36 <https://github.com/apache/cassandra/commit/23fd75f27c40462636f09920719b5dcbef5b8f36>) and this should not have lead to much larger bloom filters. 3. large sstables (few above 1 TB) have been splitted into way smaller ones (256 vnodes) during the upgrade sstables. Could this lead to the described problem with way too large bloom filters? Best, Matthias 10. Sep. 2019, 14:22 von matthias.p...@tutao.de.INVALID: > Hi there, > we just finished upgrading sstables on a single node after upgrading from > 2.2.14 to 3.11.4. Since then, we noted a drastic increase of off heap memory > consumption. This is due to increased bloom filter size. > > According to cfstats output "Bloom filter off heap memory used" increased by > a factor between 7 and 8. That means that while bloom filters took 1 GB of > off heap storage with 2.2.14, they fill around 7.5 GB with 3.11.4. > > Did anyone observe something similar? Have there been bigger changes to the > bloom filter implementation between those versions? > > Best, > Matthias > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
