[
https://issues.apache.org/jira/browse/SOLR-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350835#comment-14350835
]
Tom Burton-West commented on SOLR-7175:
---------------------------------------
Hi Mike,
Thanks for taking a look. We found a race condition in our code that resulted
in the driver thinking all the indexers were finished when they sometimes
weren't. It just happened that we inserted this bug in the code about the time
we switched from Solr 3.6 to Solr 4.10.2 so I jumped to the wrong conclusion.
I'll go ahead and close the issue.
Tom
> <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]
