Re: Ghost compaction process
Does `nodetool comactionstats` show nothing running as well? Also, for posterity what are some details of the setup (C* version, etc.)? -Tim -- Tim Heckman Operations Engineer PagerDuty, Inc. On Sun, Jun 7, 2015 at 6:40 PM, Arturas Raizys artu...@noantidot.com wrote: Hello, I'm having problem there in 1 node I have continues compaction process running and consuming CPU. nodetool tpstats show 1 compaction in progress, but if I try to query system.compactions_in_progress table, I see 0 records. This never ending compaction does slow down node and it becomes laggy. I'm willing to hire a contractor to solve this problem if anyone is interested. Cheers, Arturas
Ghost compaction process
Hello, I'm having problem there in 1 node I have continues compaction process running and consuming CPU. nodetool tpstats show 1 compaction in progress, but if I try to query system.compactions_in_progress table, I see 0 records. This never ending compaction does slow down node and it becomes laggy. I'm willing to hire a contractor to solve this problem if anyone is interested. Cheers, Arturas
Re: Ghost compaction process
Hi, Does `nodetool comactionstats` show nothing running as well? Also, for posterity what are some details of the setup (C* version, etc.)? `nodetool comactionstats` does not return anything, it just waits. If I do enable DEBUG logging, I see this line poping up while executing `nodetool compactionstats` : DEBUG [RMI TCP Connection(1856)-127.0.0.1] 2015-06-08 09:29:46,043 LeveledManifest.java:680 - Estimating [0, 0, 0, 0, 0, 0, 0, 0, 0] compactions to do for system.paxos I'm running Cassandra 2.1.14 with 7 node cluster. We're using small VM with 8GB of ram and SSD. Our data size per node with RF=2 is ~40GB. Load is ~ 1000 writes/second. Most of the data TTL is 2weeks. Cheers, Arturas
Re: Ghost compaction process
HI, Is it 2.0.14 or 2.1.4? If you are on 2.1.4 I would recommend an upgrade to 2.1.5 regardless of that issue. From the data you provide it is difficult to access what is the issue. If you are running with RF=2 you can always add another node and kill that one if that is the only node that shows that problem. With 40GB load is not a big issue. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo http://linkedin.com/in/carlosjuzarterolo* Mobile: +31 6 159 61 814 | Tel: +1 613 565 8696 x1649 www.pythian.com On Mon, Jun 8, 2015 at 4:04 AM, Arturas Raizys artu...@noantidot.com wrote: Hi, Does `nodetool comactionstats` show nothing running as well? Also, for posterity what are some details of the setup (C* version, etc.)? `nodetool comactionstats` does not return anything, it just waits. If I do enable DEBUG logging, I see this line poping up while executing `nodetool compactionstats` : DEBUG [RMI TCP Connection(1856)-127.0.0.1] 2015-06-08 09:29:46,043 LeveledManifest.java:680 - Estimating [0, 0, 0, 0, 0, 0, 0, 0, 0] compactions to do for system.paxos I'm running Cassandra 2.1.14 with 7 node cluster. We're using small VM with 8GB of ram and SSD. Our data size per node with RF=2 is ~40GB. Load is ~ 1000 writes/second. Most of the data TTL is 2weeks. Cheers, Arturas -- --
