Re: Manually deleting sstables
2) Are there any other recommended procedures for this? 0) stop writes to columnfamily 1) TRUNCATE columnfamily; 2) nodetool clearsnapshot # on the snapshot that results 3) DROP columnfamily; My two cents here is that this process is extremely difficult to automate, making testing that involves dropping column families very difficult. Robert
Re: Manually deleting sstables
You can always set autosnapshot: false in cassandra.yaml for testing environments. On Thu, Aug 21, 2014 at 9:57 AM, Robert Wille rwi...@fold3.com wrote: 2) Are there any other recommended procedures for this? 0) stop writes to columnfamily 1) TRUNCATE columnfamily; 2) nodetool clearsnapshot # on the snapshot that results 3) DROP columnfamily; My two cents here is that this process is extremely difficult to automate, making testing that involves dropping column families very difficult. Robert -- Tyler Hobbs DataStax http://datastax.com/
Manually deleting sstables
After we dropped a table, we noticed that the sstables are still there. After searching through the forum history, I noticed that this is known behavior. 1) Is there any negative impact of deleting the sstables off disk and then restarting Cassandra? 2) Are there any other recommended procedures for this? Thanks, Parag
Re: Manually deleting sstables
On Tue, Aug 19, 2014 at 8:59 AM, Parag Patel ppa...@clearpoolgroup.com wrote: After we dropped a table, we noticed that the sstables are still there. After searching through the forum history, I noticed that this is known behavior. Yes, it's providing protection in this case, though many people do not expect this. 1) Is there any negative impact of deleting the sstables off disk and then restarting Cassandra? You don't have to restart Cassandra, and no. 2) Are there any other recommended procedures for this? 0) stop writes to columnfamily 1) TRUNCATE columnfamily; 2) nodetool clearsnapshot # on the snapshot that results 3) DROP columnfamily; =Rob
