Compaction time is proportional to the size of the sstable, yes. Not sure how it could be otherwise. And it does generate a lot of garbage. So unless you are seeing concurrent failures in the GC and corresponding large pause times, your heap should be fine, as long as the rows you are compacting aren't too large.
2010/4/28 casablinca126.com <casabli...@126.com>: > hi, > The compaction process is very slow, when the size of new generating > sstable file grows upon 25GB; > at the meantime, the garbage collector is running frequently. > Firstly, I have a question that, is there a limitation of the sstable > size? if not, is 2GB heap size not > enough for processing such a large file? > I'm using cassandara-0.6.1, the heap size of jvm is 2GB(maximum in > 32-bit system) . > > Thanks in advance ! > Best Regards, > Cao Jiguang > > -------------- > casablinca126.com > 2010-04-28 > > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
