The truncation was performed via OpsCenter, which I believe is ALL by default.
From: Rahul Singh <rahul.xavier.si...@gmail.com> Sent: Thursday, August 23, 2018 6:55 PM To: user@cassandra.apache.org Subject: Re: Cassandra 2.2.7 Compaction after Truncate issue 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 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<mailto: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<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCASSANDRA-7803&data=02%7C01%7C%7C550fca06044f40204c5208d6095c3775%7C0f96d359c20349d1a42dcbb27249db0d%7C0%7C0%7C636706689017092471&sdata=MtnHkiRuQsYmy6FyHqOGIUixRc30dz3k3wEOlAeWobg%3D&reserved=0> Any ideas? Thanks, David Payne |￣￣| ＿☆☆☆＿ （ ´_⊃｀） c. 303-717-0548<tel:303-717-0548> dav...@cqg.com<mailto:dav...@cqg.com>
