Re: Core size - distinguish between merge and deletes

2017-11-09 Thread Erick Erickson
Please don't do that ;) Unless you're willing to do it frequently. See: https://lucidworks.com/2017/10/13/segment-merging-deleted-documents-optimize-may-bad/ expungeDeletes is really a variety of optimize, so the issues outlined in that blog apply. Best, Erick On Thu, Nov 9, 2017 at 12:24 PM, S

Re: Core size - distinguish between merge and deletes

2017-11-09 Thread Shashank Pedamallu
Thanks for the response Erick. I’m deleting the documents with expungeDeletes option set as true. So, that does trigger a merge to throw away the deleted documents. On 11/9/17, 12:17 PM, "Erick Erickson" wrote: bq: Is there a way to distinguish between when size is being reduced becaus

Re: Core size - distinguish between merge and deletes

2017-11-09 Thread Erick Erickson
bq: Is there a way to distinguish between when size is being reduced because of a delete from that of during a lucene merge. Not sure what you're really looking for here. Size on disk is _never_ reduced by a delete operation, the document is only 'marked as deleted'. Only when segments are merged

Re: core size

2009-11-17 Thread Lance Norskog
Been there done that. Indexing into the smaller cores will be faster. You will be able to spread the load across multiple machines. There are other advantages: You will not have a 1/2Terabyte set of files to worry about. You will not need 1.1T in one partition to run an optimize. You will not nee

Re: core size

2009-11-16 Thread Otis Gospodnetic
If an index fits in memory, I am guessing you'll see the speed change roughly proportionally to the size of the index. If an index does not fit into memory (i.e. disk head has to run around the disk to look for info), then the improvement will be even greater. I haven't explicitly tested this