[
https://issues.apache.org/jira/browse/SOLR-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026133#comment-14026133
]
Anshum Gupta commented on SOLR-6123:
------------------------------------
Allowing both would actually not even be a test. It's a tough thing to actually
test as the time taken for split and the clusterstatus api is subject to other
variables and the tasks might complete sooner than expected.
This would certainly reduce the chances of the test failing, though certainly
not guarantee success always.
> The 'clusterstatus' API filtered by collection times out if a long running
> operation is in progress
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-6123
> URL: https://issues.apache.org/jira/browse/SOLR-6123
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.9
> Reporter: Shalin Shekhar Mangar
> Assignee: Anshum Gupta
> Fix For: 4.9
>
> Attachments: SOLR-6123.patch, SOLR-6123.patch
>
>
> If a long running shard split is in progress, say for collection=X, then
> clusterstatus API with collection=X will time out.
> The OverseerCollectionProcessor should never block an operation such as
> clusterstatus even if there are tasks for the same collection in progress.
> This bug was introduced by SOLR-5681.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
