Sorry, I should have given more background. We have, at the moment 3.8
million documents of 0.7MB/doc average so we have extremely large
shards. We build about 400,000 documents to a shard resulting
200GB/shard. We are also using LVM snapshots to manage a snapshot of
the shard which we serve
: Is it possible to tell Solr or Lucene, when optimizing, to write the files
: that constitute the optimized index to somewhere other than
: SOLR_HOME/data/index or is there something about the optimize that requires
: the final segment to be created in SOLR_HOME/data/index?
For what
Hmm... Interesting question, not that I know of. The only way
one could do this would be to intercept the newly optimized
files via a FileSwitchDirectory like implementation that knows
which new files are optimized and should underneath go to a
different physical path.
On Mon, Sep 28, 2009 at
The optimize operation happens in place.
I've been told that if you set mergeFactor=2 when indexing, it will
be slower but you will always have a mostly optimized index.
On Mon, Sep 28, 2009 at 10:22 AM, Jason Rutherglen
jason.rutherg...@gmail.com wrote:
Hmm... Interesting question, not that I
, HBase, UIMA, NLP, NER, IR
- Original Message
From: Lance Norskog goks...@gmail.com
To: solr-user@lucene.apache.org
Sent: Monday, September 28, 2009 2:42:29 PM
Subject: Re: Writing optimized index to different storage?
The optimize operation happens in place.
I've been told
, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
From: Lance Norskog goks...@gmail.com
To: solr-user@lucene.apache.org
Sent: Monday, September 28, 2009 2:42:29 PM
Subject: Re: Writing optimized index to different storage?
The optimize operation happens in place.
I've been
