[
https://issues.apache.org/jira/browse/SOLR-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Burton-West updated SOLR-7175:
----------------------------------
Attachment: build-1.indexwriterlog.2015-02-23.gz
Attached is an indexwriter log where after a large merge down to 2 segments,
startFullFlush was called and found additional docs in ram which were then
written to 2 new segments.These new segments were not merged so the end result
of calling <optimize maxSegments=2> was a shard with 4 segments.
Attached also is our solrconfig.xml file in case the problem is caused by some
configuration error that overides the maxSegments=2.
> <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
>
>
> 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]
