On Wed, Aug 20, 2014 at 3:45 PM, Kevin Burton <[email protected]> wrote:
> So , right now, I have a full cassandra cluster… all my nodes are down. > When your cluster is down, #cassandra is probably a better outlet than cassandra-user@. > And I have a table, which I could just issue a truncate command to. It's > just a log table so dropping the data is fine. > > but instead, I can't do that because my cluster is completely offline. > > Now, the disk failure policy of stop is still ideal, because I don't want > INSERTs to partially work, but having some type of basic data manipulation > CQL like DROP TABLE or TRUNCATE TABLE would be nice. > +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. > 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 2) Add disk space to your node. This may not be possible. =Rob
