> But, that is still awkward. Does cleanup take so much disk space to
complete the compaction operation? In other words, twice the size?
Not really, but logically yes.
According to 1.0.7 source, cleanup checks if there's enough space that is
larger than the worst scenario as below. If not, the ex
Thanks for the answers.
I got it. I was using cleanup, because I thought it would delete the
tombstones.
But, that is still awkward. Does cleanup take so much disk space to
complete the compaction operation? In other words, twice the size?
*Atenciosamente,*
*Víctor Hugo Molinar - *@vhmolinar
Hi Victor,
As Andrey said, running cleanup doesn't work as you expect.
> The reason I need to clean things is that I wont need most of my
inserted data on the next day.
Deleted objects(columns/records) become deletable from sstable file when
they get expired(after gc_grace_seconds).
Such d
On Tue, May 28, 2013 at 7:39 AM, Víctor Hugo Oliveira Molinar
wrote:
> So I'd like to know more about what does happens in a cleanup operation.
> Appreciate any help.
./src/java/org/apache/cassandra/db/compaction/CompactionManager.java"
line 591 of 1175
"
logger.info("Cleaning up " + sstable);
cleanup removes data which doesn't belong to the current node. You have to
run it only if you move (or add new) nodes. In your case there is no any
reason to do it.
On Tue, May 28, 2013 at 7:39 AM, Víctor Hugo Oliveira Molinar <
vhmoli...@gmail.com> wrote:
> Hello everyone.
> I have a daily main
Hello everyone.
I have a daily maintenance task at c* which does:
-truncate cfs
-clearsnapshots
-repair
-cleanup
The reason I need to clean things is that I wont need most of my inserted
data on the next day. It's kind a business requirement.
Well, the problem I'm running to, is the misundersta