[
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-4.iw.2015-02-25.txt.gz
Previous file did not have an explicit commit.
This file: build-4.iw.2015-02-25.txt includes a restart of Solr, a commit, and
then the optimize maxSegments=2. Same scenario where after the major merge
down to 2 segments a flush finds docs in ram and additional segments are
written to disk.
> <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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
