[
https://issues.apache.org/jira/browse/SOLR-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517863#comment-14517863
]
Anshum Gupta commented on SOLR-7481:
------------------------------------
That is how all the Collections API work. They silently ignore the params that
aren't supported.
Unless there's something else going on here that I'm missing, I think we could
just close this issue.
> DELETESHARD does not support async API
> --------------------------------------
>
> Key: SOLR-7481
> URL: https://issues.apache.org/jira/browse/SOLR-7481
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.0
> Reporter: Ian Rose
> Priority: Minor
>
> My local testing shows that DELETESHARD ignores the async parameter. If I
> try an async DELETESHARD like so:
> http://localhost:8983/solr/admin/collections?action=deleteshard&collection=2Gp&shard=shard1_0_0&async=12-foo-4
> The response includes the command result, indicating that the command was not
> run async:
> <lst name="success">
> <lst name="192.168.1.106:8983_solr">
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">16</int>
> </lst>
> </lst>
> </lst>
> And in addition REQUESTSTATUS calls for that requestId fail with "Did not
> find taskid [12-foo-4] in any tasks queue".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
