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
