Does cassandra suffer from this same issue in 0.7? You would think it
would at least warn if not prevent anticompaction if it knows there is a
good chance of running out of space.
On 12/8/10 8:05 AM, Jake Maizel wrote:
I was in a similar situation and luckily had snapshots to clear and
gain sp
I was in a similar situation and luckily had snapshots to clear and
gain space but you are correct. I would be careful of using the disk
more than 50% as the anit-compaction during cleanup could fail.
I don't have any experience with adding a data directory on the fly.
On Wed, Dec 8, 2010 at 4:5
Did both but didn't seem to help. I have another drive on that machine
with some free space. If I add another directory to the
DataFileDirectory config and restart, will it start using that directory?
Anything else I can do?
This actually leads me to an important question. Should I always make
Also, look for any snapshots that can be cleared with nodetool
clearsnapshot or just run the command to remove any that exist.
On Wed, Dec 8, 2010 at 9:04 AM, Oleg Anastasyev wrote:
>
> Mark gmail.com> writes:
>
>> Caused by: java.lang.RuntimeException: Insufficient disk space to flush
>> a
Mark gmail.com> writes:
> Caused by: java.lang.RuntimeException: Insufficient disk space to flush
> at
> >
> On 12/7/10 8:44 PM, Mark wrote:
> > 3 Node cluster and I just ran a nodetool cleanup on node #3. 1 and 2
> > are now at 100% disk space. What should I do?
>
>
Is there files w
Tried restarting node #1 and now received:
Caused by: java.lang.RuntimeException: Insufficient disk space to flush
at
org.apache.cassandra.db.ColumnFamilyStore.getFlushPath(ColumnFamilyStore.java:442)
at
org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:149)
at org
3 Node cluster and I just ran a nodetool cleanup on node #3. 1 and 2 are
now at 100% disk space. What should I do?
