thank you shay.... from your answer, i am getting some doubts.....
How to identify that there optimization process is happening in
While optimizing index, is it possible to access an index and
process on it...?
How long does the optimization process will take....?
On May 6, 8:22 pm, Shay Banon shay.ba...@elasticsearch.com wrote:
On Friday, May 6, 2011 at 8:30 AM, senthil prabhu wrote:
I have few questions about Optimize operation in Elastic search
- What is the optimization actually doing and How long does it take?
Internally, each Lucene index is consisted of several internal segments. On going, Lucene maintains keeping the number of segments at 10 (configurable) by continuously merging segments.
In general, less segments means faster searches and less memory usage, but, more merging required if indexing is done.> 2. What situations or requirements will cause Elastic Search to start
Lucene actually maintains that based on the configurable number of segments per index (shard).> 3. Are there options to when an optimization will start? Or is it
always automatic at the discretion of ES.
4. What are the results if ES is not optimized?
It is always keeps on being optimized. The optimization API allows to explicitly optimize the index.