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 <springrider@gmail.com> wrote:
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         Status State   Load            Owns    Token                                       
                                                       113427455640312821154458202477256070484     
node1      Up     Normal  43 GB           33.33%  0                                           
node2     Up     Normal  59.52 GB        33.33%  56713727820156410577229101238628035242      
node3      Down   Normal  142.57 GB       33.33%  113427455640312821154458202477256070484