And let's not forget the interesting bug in MMapDirectory:
http://lucene.apache.org/core/old_versioned_docs/versions/3_5_0/api/all/org/apache/lucene/store/MMapDirectory.html
"NOTE: memory mapping uses up a portion of the virtual memory address space in
your process equal to the size of the file
Optimzing will _temporarily_ double the index size,
but it shouldn't be permanent. Is it possible that
you have inadvertently told Solr to keep an extra
snapshot? I think it's "numberToKeep" in your
replication handler, but I'm going from memory here.
Best
Erick
On Fri, Jun 14, 2013 at 2:15 AM,
Hi,
i have replicate my index from 1.4 to 3.5 and after replication i try
optimize the index in 3.5 with below URL.
http://localhost:9002/solr35/collection1/update?optimize=true&commit=true
when i optimize the index in 3.5, it's increase the index size to double.
in 1.4 the size of index is 428G
