On Wed, Aug 20, 2014 at 4:24 PM, Kevin Burton 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 d
>
>
>> +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 f
On Wed, Aug 20, 2014 at 3:45 PM, Kevin Burton 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
>
So , right now, I have a full cassandra cluster… all my nodes are down.
Fun!
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 poli
