[
https://issues.apache.org/jira/browse/SOLR-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350575#comment-14350575
]
Tom Burton-West commented on SOLR-7175:
---------------------------------------
Hi Mike,
Our code is supposed to completely finish indexing before then calling a commit
and optimize.
I was trying to figure out how indexed documents could be in RAM after we
called a commit and the resulting flush finished. Indexing should have
completed prior to our code calling a commit and then optimize (ie. force
merge). We will double check our code and of course if we find a bug in the
code we'll fix the bug, test, and close the issue. The reason we suspected
something on the Solr4/Lucene4 end is that we haven't made any changes to the
indexing/optimizing code in quite a while and we were not seeing this issue
with Solr 4.6.
> <optimize maxSegments="2"/> results in more than 2 segments after optimize
> finishes
> -----------------------------------------------------------------------------------
>
> Key: SOLR-7175
> URL: https://issues.apache.org/jira/browse/SOLR-7175
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10.2
> Environment: linux
> Reporter: Tom Burton-West
> Priority: Minor
> Attachments: build-1.indexwriterlog.2015-02-23.gz,
> build-4.iw.2015-02-25.txt.gz, solr4.shotz
>
>
> After finishing indexing and running a commit, we issue an <optimize
> maxSegments="2"/> to Solr. With Solr 4.10.2 we are seeing one or two shards
> (out of 12) with 3 or 4 segments after the optimize finishes. There are no
> errors in the Solr logs or indexwriter logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
