Thanks a lot, Aaron. Our cluster is much stable now. We'll look at
upgrading to 1.x in the coming weeks.
On Tue, Mar 6, 2012 at 2:33 PM, aaron morton wrote:
> 1)Since you mentioned hard links, I would like to add that our data
> directory itself is a sym-link. Could that be causing an issue ?
>
>
> 1)Since you mentioned hard links, I would like to add that our data directory
> itself is a sym-link. Could that be causing an issue ?
Seems unlikely.
> I restarted the node and it went about deleting the files and the disk space
> has been released. Can this be done using nodetool, and witho
Hi Aaron,
1)Since you mentioned hard links, I would like to add that our data
directory itself is a sym-link. Could that be causing an issue ?
2)Yes, there are 0 byte files of the same numbers
in Keyspace1 directory
0 Mar 4 01:33 Standard1-g-7317-Compacted
0 Mar 3 22:58 Standard1-g-7968-Compact
> It seems that instead of removing the snapshot, clearsnapshot moved the data
> files from the snapshot directory to the parent directory and the size of the
> data for that keyspace has doubled.
That is not possible, there is only code there to delete a files in the
snapshot.
Note that in th
Version 0.8.9
We run a 2 node cluster with RF=2. We ran a scrub and after that ran the
clearsnapshot to remove the backup snapshot created by scrub. It seems that
instead of removing the snapshot, clearsnapshot moved the data files from
the snapshot directory to the parent directory and the size o
