On Sun, Jul 13, 2014 at 5:32 AM, Michael McCandless <[email protected]> wrote:
For the index close, I didn't issue any command, elasticsearch seemed to >> do that on its own. The code is in IndexingMemoryController. The triggering >> event seems to be the ram buffer size change, this triggers a call to >> InternalEngine.updateIndexingBufferSize() which then calls flush with type >> NEW_WRITER. That seems to close the lucene IndexWriter. >> > > Ahh, thanks for the clarification, yes ES sometimes closes & opens a new > writer to make "non-live" settings changes take effect. However, changing > RAM buffer size for indexing is a live setting so it should not require the > close/open yet indeed (InternalEngine.updateIndexingBufferSize) it does ... > I'll dig. > OK, this is now fixed in Elasticsearch (will be in 1.3.0) ... see https://github.com/elasticsearch/elasticsearch/pull/6856 so now when the indexing RAM buffer is updated it won't close & reopen the IndexWriter. Mike McCandless http://blog.mikemccandless.com -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAD7smRcROO5LSxP5CTzv6tT0_TKAVKXfa10bPKaQU-6JRLM3AQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
