lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijiang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LUCENE-5800) When using NRTCachingDirectory, if the new created segment is in compound format, it is always created in cache(RAMDirectory). It will cause large segments referenced by IndexSearcher in memory.
Date Tue, 01 Jul 2014 08:36:24 GMT
Zhijiang Wang created LUCENE-5800:
-------------------------------------

             Summary: When using NRTCachingDirectory, if the new created segment is in compound
format, it is always created in cache(RAMDirectory). It will cause large segments referenced
by IndexSearcher in memory. 
                 Key: LUCENE-5800
                 URL: https://issues.apache.org/jira/browse/LUCENE-5800
             Project: Lucene - Core
          Issue Type: Bug
          Components: core/store
            Reporter: Zhijiang Wang


When using NRTCachingDirectory, if the new created segment is in compound format,  in the
method of createOutput(String name,IOContext context), the real context is not used and uses
IOContext.DEFAULT instead. So the estimatedMergeBytes or estimatedSegmentSize will always
be smaller than maxMergeSizeBytes,maxCachedBytes, resulting in new created compound segment
is always in cache(RAMDirectory).  And these new large segments created by merging will be
referenced by ReaderPool in the IndexWriter when using NRT feature, resulting in much memory
used in process and actually these referenced large segments has already been sync to disk
when commit.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message