You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andy Laird (JIRA)" <ji...@apache.org> on 2012/06/08 18:57:23 UTC
[jira] [Created] (SOLR-3527) Optimize ignores maxSegments in
distributed environment
Andy Laird created SOLR-3527:
--------------------------------
Summary: Optimize ignores maxSegments in distributed environment
Key: SOLR-3527
URL: https://issues.apache.org/jira/browse/SOLR-3527
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 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3527) SolrCmdDistributor drops some of the
important commit attributes (maxOptimizeSegments, softCommit,
expungeDeletes) when sending a commit to replicas.
Posted by "Commit Tag Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494982#comment-13494982 ]
Commit Tag Bot commented on SOLR-3527:
--------------------------------------
[branch_4x commit] Mark Robert Miller
http://svn.apache.org/viewvc?view=revision&revision=1384969
SOLR-3527: SolrCmdDistributor drops some of the important commit attributes (maxOptimizeSegments, softCommit, expungeDeletes) when sending a commit to replicas.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3527) SolrCmdDistributor drops some of the
important commit attributes (maxOptimizeSegments, softCommit,
expungeDeletes) when sending a commit to replicas.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3527) SolrCmdDistributor drops some of the
important commit attributes (maxOptimizeSegments, softCommit,
expungeDeletes) when sending a commit to replicas.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-3527.
-------------------------------
Resolution: Fixed
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3527) Optimize ignores maxSegments in
distributed environment
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3527:
------------------------------
Component/s: SolrCloud
Priority: Critical (was: Major)
Fix Version/s: 5.0
4.0
> Optimize ignores maxSegments in distributed environment
> -------------------------------------------------------
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3527) Optimize ignores maxSegments in
distributed environment
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291890#comment-13291890 ]
Mark Miller commented on SOLR-3527:
-----------------------------------
Sounds right Andy - thanks for the report.
> Optimize ignores maxSegments in distributed environment
> -------------------------------------------------------
>
> Key: SOLR-3527
> URL: https://issues.apache.org/jira/browse/SOLR-3527
> 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 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3527) Optimize ignores maxSegments in
distributed environment
Posted by "Andy Laird (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291864#comment-13291864 ]
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: https://issues.apache.org/jira/browse/SOLR-3527
> 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 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org