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 <gokoproj...@gmail.com> wrote: > 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 <surbhi.gupt...@gmail.com> > 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 is corrupt then compaction kind of hangs. >> Try to run nodetool scrub ... >> >> On 8 August 2016 at 09:34, John Wong <gokoproj...@gmail.com> wrote: >> >>> On Mon, Aug 8, 2016 at 11:16 AM, Surbhi Gupta <surbhi.gupt...@gmail.com> >>> 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 so this would be a temporary solution, as the root issue is the >>> compaction won't finish. I see nothing in the log. FYI, gathering more info >>> from the developer, this CF stores large rows. >>> >>> If anyone ever encountered similar issue, please let me know. >>> >>> John >>> >> >> >
