You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Dipan Shah <di...@hotmail.com> on 2019/12/02 07:26:41 UTC

No progress in compactionstats

Hello,

I am running a 5 node Cassandra cluster on V 3.7 and did not understand why the following thing was happening. I had altered the compaction strategy of a table from Size to Leveled and while running "nodetool compactionstats" found that the SSTables were stuck and not getting compacted. This was happening on majority of the nodes while the remaining were still showing some progress at compacting the SSTables.

[cid:9eca23a8-c11c-4ace-8409-5400b9d93aab]

There were no errors in system.log and a service restart also did not help. I reverted the compaction strategy to Size to see what happens and that sent the value of pending tasks back to 0.

I have done this earlier for a similar tables and it has worked perfectly fine for me. What could have gone wrong over here?


Thanks,

Dipan Shah

Re: No progress in compactionstats

Posted by Hossein Ghiyasi Mehr <gh...@gmail.com>.
Hi,
Check nodetool tpstats output.
*-------------------------------------------------------*
*VafaTech <http://www.vafatech.com> : A Total Solution for Data Gathering &
Analysis*
*-------------------------------------------------------*


On Mon, Dec 2, 2019 at 10:56 AM Dipan Shah <di...@hotmail.com> wrote:

> Hello,
>
> I am running a 5 node Cassandra cluster on V 3.7 and did not understand
> why the following thing was happening. I had altered the compaction
> strategy of a table from Size to Leveled and while running "nodetool
> compactionstats" found that the SSTables were stuck and not getting
> compacted. This was happening on majority of the nodes while the remaining
> were still showing some progress at compacting the SSTables.
>
>
>
> There were no errors in system.log and a service restart also did not
> help. I reverted the compaction strategy to Size to see what happens and
> that sent the value of pending tasks back to 0.
>
> I have done this earlier for a similar tables and it has worked perfectly
> fine for me. What could have gone wrong over here?
>
> Thanks,
>
> Dipan Shah
>