I have ever modify the code to set INDEX_INTERVAL = 512, to decrease the memory usage. And it seems working fine. Is it right?
2010/4/30 casablinca126.com <casabli...@126.com> > hi, > It seems changing the INDEX_INTERVAL with conflict with > AntiEntropyService, right? > I will reconstruct my sstables. > Thank you, Jonathan! > cheers, > Cao Jiguang > > > ------------------ > casablinca126.com > 2010-04-30 > > ------------------------------------------------------------- > 发件人：Jonathan Ellis > 发送日期：2010-04-29 20:54:03 > 收件人：u...@cassandra.apache.org > 抄送： > 主题：Re: Re: compaction slow while sstable>25GB,limitation of thesstablesize? > > 2010/4/29 casablinca126.com <casabli...@126.com>: > > Hi, > > ???�Now I start to know what's really happenning. The INDEX_INTERVAL(in > IndexSummary.java) was set to be 4; so at least 1/4 > > of the indices are in the heap. For a node with 20M columns, most of the > heap is occupied by indices, and of course a poor performance > > with processing large files. > > ???�Is it possible to modify the INDEX_INTERVAL without reconstruct the > sstables? I modified the code, �and restart every node, > > but "NotFoundException()" is reported when read the columns. > > No. INDEX_INTERVAL is not intended to be configurable. (It is > all-caps, the convention for constants...) > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com >
