you may go OS level to delete the files.That's what I did before. Truncate action is frequently failed on some remote nodes in a heavy transactions env.
Thanks, James On Thu, Aug 23, 2018 at 8:54 PM, Rahul Singh <rahul.xavier.si...@gmail.com> wrote: > David , > > What CL do you set when running this command? > > Rahul Singh > Chief Executive Officer > m 202.905.2818 > > Anant Corporation > 1010 Wisconsin Ave NW, Suite 250 > <https://maps.google.com/?q=1010+Wisconsin+Ave+NW,+Suite+250+%0D%0AWashington,+D.C.+20007&entry=gmail&source=g> > Washington, D.C. 20007 > > We build and manage digital business technology platforms. > On Aug 14, 2018, 11:49 AM -0500, David Payne <dav...@cqg.com>, wrote: > > Scenario: Cassandra 2.2.7, 3 nodes, RF=3 keyspace. > > > > Truncate a table. > > More than 24 hours later… FileCacheService is still reporting cold readers > for sstables of truncated data for node 2 and 3, but not node 1. > > The output of nodeool compactionstats shows stuck compaction for the > truncated table for node 2 and 3, but not node 1. > > > > This appears to be a defect that was fixed in 2.1.0. > https://issues.apache.org/jira/browse/CASSANDRA-7803 > > > > Any ideas? > > > > Thanks, > > David Payne > > |￣￣| > ＿☆☆☆＿ > （ ´_⊃｀） > > c. 303-717-0548 > > dav...@cqg.com > > > >
