On 12/21/06, Michael McCandless <[EMAIL PROTECTED]> wrote:
Harini Raghavan wrote:
> I am using lucene 1.9.1 for search functionality in my j2ee application
> using JBoss as app server. The lucene index directory size is almost 20G
> right now. There is a Quartz job that is adding data to the index evey
> min and around 20000 documents get added to the index every day.When the
> documents are added and the segments are merged, the index size
> increases and sometimes grows to more than double its original size.
> This results in filling up the disk space. We have allotted a f/s size
> of 50G and even that is not sufficient at times. Is there an optimum
> vales for the f/s size to be allotted in such scenario.
> Any suggestions would be appreciated.
I believe optimize should use at most 2X the starting index size,
transiently, if there are no readers open against the index.
Isn't it up to 3x with the compound index format? (and 4x with readers opened)
-Yonik
http://incubator.apache.org/solr Solr, the open-source Lucene search server
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
