The truncation was performed via OpsCenter, which I believe is ALL by default.
From: Rahul Singh
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
I was able to resolve the issue with a rolling restart of the cluster.
From: James Shaw
Sent: Thursday, August 23, 2018 7:52 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra 2.2.7 Compaction after Truncate issue
you may go OS level to delete the files.That's what I did before. Tru
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
wrote:
> David ,
>
> What CL do you set when running this command?
>
> Rahul Sing
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 , wrote:
> S
Scenario: Cassandra 2.2.7, 3 nodes, RF=3 keyspace.
1. Truncate a table.
2. 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.
3. The output of nodeool compactionstats shows stuck compacti
