Re: LEAK DETECTED while minor compaction

2018-02-24 Thread Jay Zhuang
Maybe it's because of https://issues.apache.org/jira/browse/CASSANDRA-12014 We had the similar issue in 3.0.14, when the SSTable has more than about 51 million keys: https://issues.apache.org/jira/browse/CASSANDRA-13785 If you upgrade to 2.2.11+, you should be able to see the real compaction

Re: LEAK DETECTED while minor compaction

2018-02-21 Thread Дарья Меленцова
Bloom filter settings have not changed, they are default. In the table settings bloom_filter_fp_chance = 0.01. Should I increase it? DESC TABLE "PerBoxEventSeriesEventIds" CREATE TABLE "EventsKeyspace"."PerBoxEventSeriesEventIds" ( key blob, column1 text, value blob, PRIMARY KEY

Re: LEAK DETECTED while minor compaction

2018-02-20 Thread Jeff Jirsa
Your bloom filter settings look broken. Did you set the FP ratio to 0? If so that’s a bad idea and we should have stopped you from doing it. -- Jeff Jirsa > On Feb 20, 2018, at 11:01 PM, Дарья Меленцова wrote: > > Hello. > > Could you help me with LEAK DETECTED error

LEAK DETECTED while minor compaction

2018-02-20 Thread Дарья Меленцова
Hello. Could you help me with LEAK DETECTED error while minor compaction process? There is a table with a lot of small record 6.6*10^9 (mapping (eventId, boxId) -> cellId)). Minor compaction starts and then fails on 99% done with an error: Stacktrace ERROR [Reference-Reaper:1] 2018-02-05