[
https://issues.apache.org/jira/browse/SOLR-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-3527:
------------------------------
Summary: SolrCmdDistributor drops some of the important commit attributes
(maxOptimizeSegments, softCommit, expungeDeletes) when sending a commit to
replicas. (was: Optimize ignores maxSegments in distributed environment)
> SolrCmdDistributor drops some of the important commit attributes
> (maxOptimizeSegments, softCommit, expungeDeletes) when sending a commit to
> replicas.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3527
> URL: https://issues.apache.org/jira/browse/SOLR-3527
> Project: Solr
> Issue Type: Bug
> Components: SearchComponents - other, SolrCloud
> Affects Versions: 4.0-ALPHA
> Reporter: Andy Laird
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.0, 5.0
>
>
> Send the following command to a Solr server with many segments in a
> multi-shard, multi-server environment:
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
