I have faced similar kind of issue while we were using LCS ...
We ran the scrub and it was helpful to clear the corruption and compaction
caught up well after that ...
On 8 August 2016 at 13:23, John Wong wrote:
> Hi.
>
> I don't see any error logs indicate corrupted sstable error. Is it safe t
Hi.
I don't see any error logs indicate corrupted sstable error. Is it safe to
run this?
Thanks.
On Mon, Aug 8, 2016 at 1:18 PM, Surbhi Gupta
wrote:
> Can you see if any of the sstable is corrupt ?
> I have seen with my past experience , if any of the sstable which is part
> of the compaction
Can you see if any of the sstable is corrupt ?
I have seen with my past experience , if any of the sstable which is part
of the compaction is corrupt then compaction kind of hangs.
Try to run nodetool scrub ...
On 8 August 2016 at 09:34, John Wong wrote:
> On Mon, Aug 8, 2016 at 11:16 AM, Surbh
On Mon, Aug 8, 2016 at 11:16 AM, Surbhi Gupta
wrote:
> Once you restart a node compaction will start automatically, if u dont
> want to do so then do
> nodetool disableautocompaction as soon as node is started .
>
>
Thanks. I certainly can give that a try for the specific column family, but
even
Once you restart a node compaction will start automatically, if u dont want
to do so then do
nodetool disableautocompaction as soon as node is started .
On 8 August 2016 at 07:22, John Wong wrote:
> Hi
>
> We have a compaction stuck. No progress ever made.
>
> nodetool compactionstats
> pending
Hi
We have a compaction stuck. No progress ever made.
nodetool compactionstats
pending tasks: 2
compaction typekeyspace column family
completed total unit progress
Compactionmy_columnfamily 0
410383527 bytes 0.00%
Active
