On 09/19/2011 04:26 AM, Anand Somani wrote:
In my tests I have seen repair sometimes take a lot of space (2-3
times), cleanup did not clean it, the only way I could clean that was
using major compaction.
Do you remember with what version you saw these problems?
I've had the same problems with
I am using 0.7.4 too. and would waiting for 0.8.6 stable to release because
of CASSANDRA-3166.
did you already using 0.8.6 in production?
2011/9/19 Jonas Borgström jonas.borgst...@trioptima.com
On 09/19/2011 04:26 AM, Anand Somani wrote:
In my tests I have seen repair sometimes take a lot of
In my tests I have seen repair sometimes take a lot of space (2-3 times),
cleanup did not clean it, the only way I could clean that was using major
compaction.
https://issues.apache.org/jira/browse/CASSANDRA-2816 (follow links to
other jiras)
got it, thanks!
On Tue, Sep 20, 2011 at 12:27 AM, Peter Schuller
peter.schul...@infidyne.com wrote:
In my tests I have seen repair sometimes take a lot of space (2-3 times),
cleanup did not clean it, the only way I could clean that was using major
compaction.
while doing repair on node3, the Load keep increasing, suddenly cassandra
has encountered OOM, and the Load stopped at 140GB, after cassandra came
back, I tried node cleanup but it seems not working
does node repair generate many temp sstables? how to get rid of them?
thanks!
Address
In my tests I have seen repair sometimes take a lot of space (2-3 times),
cleanup did not clean it, the only way I could clean that was using major
compaction.
On Sun, Sep 18, 2011 at 6:51 PM, Yan Chunlu springri...@gmail.com wrote:
while doing repair on node3, the Load keep increasing,
so does major compaction actually clean it or merge it, I am afraid it
give me a single large file
On Mon, Sep 19, 2011 at 10:26 AM, Anand Somani meatfor...@gmail.com wrote:
In my tests I have seen repair sometimes take a lot of space (2-3 times),
cleanup did not clean it, the only way I