[
https://issues.apache.org/jira/browse/SOLR-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349270#comment-14349270
]
Michael McCandless commented on SOLR-7175:
------------------------------------------
Hmm from the IW log it looks like findForcedMerges ran, merged down to 2
segments, and then after that succeeded, IW.commit was called, but there were
some indexed documents in RAM so they were flushed to two new segments. Was
indexing happening while force merge was running?
> <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]
