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
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 comp
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
wrote:
> Hello,
>
> I'm having problem there in 1 node
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 lagg