lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Laird (JIRA)" <>
Subject [jira] [Commented] (SOLR-3527) Optimize ignores maxSegments in distributed environment
Date Fri, 08 Jun 2012 17:01:26 GMT


Andy Laird commented on SOLR-3527:

One additional data point:  the distrib=false does not matter with current behavior.  It seems
if distrib=false only the local server should be optimized (to the requested value) and if
distrib=true (default) all shards in the index should be optimized with N max segments.
> Optimize ignores maxSegments in distributed environment
> -------------------------------------------------------
>                 Key: SOLR-3527
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 4.0
>            Reporter: Andy Laird
> Send the following command to a Solr server with many segments in a multi-shard, multi-server
> curl "http://localhost:8080/solr/update?optimize=true&waitFlush=true&maxSegments=6&distrib=false"
> The local server will end up with the number of segments at 6, as requested, but all
other shards in the index will be optimized with maxSegments=1, which takes far longer to
complete.  All shards should be optimized to the requested value of 6.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message