On Wed, Aug 20, 2014 at 4:24 PM, Kevin Burton <bur...@spinn3r.com> wrote:
> >>> +1, though because you can't drop the snapshots those two commands >> automatically create (if the snapshot-before-DROP even works with disk >> full, which it probably doesn't...) you still need access to the machines >> to reclaim your disk space. >> >> > > True.. I actually disabled the snapshot feature for this reason. > > A "without snapshot" feature to drop/truncate table would be nice. > https://issues.apache.org/jira/browse/CASSANDRA-3710 Provides this, doesn't it? > And realistically, how do you even recover from this situation? You can't >>> compact the table, and you can't delete data or truncate the table either. >>> >> >> 1) Delete some SSTables on the OS level and restart Cassandra. This is >> obviously bad for consistency. >> OR >> > > Yes… luckily our tables are partitioned by day so I just deleted the > oldest day. > Yeah, lucky you. :D > 2) Add disk space to your node. This may not be possible. >> > > Yes… it's not possible because you can't compact the table without some > minor amount of disk space :-/ > No, I mean ADD DISK CAPACITY TO THE SYSTEM by f/e plugging in a USB drive or mounting a network disk. =Rob
