Hi Ian, DELETESHARD doesn't support ASYNC calls officially. We could certainly do with a better response but I believe with most of the Collections API calls at this time in Solr, you could send random params which would get ignored. Therefore, in this case, I believe that the async param gets ignored.
The go-to reference point to check what's supported is the official reference guide: https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api7 This doesn't mentioned support for async DELETESHARD calls. On Tue, Apr 28, 2015 at 8:05 AM, Ian Rose <ianr...@fullstory.com> wrote: > Is it possible to run DELETESHARD commands in async mode? Google searches > seem to indicate yes, but not definitively. > > My local experience indicates otherwise. If I start with an async > SPLITSHARD like so: > > > http://localhost:8983/solr/admin/collections?action=splitshard&collection=2Gp&shard=shard1_0_0&async=12-foo-1 > > Then I get back the expected response format, with <str name="requestid"> > 12-foo-1</str> > > And I can later query for the result via REQUESTSTATUS. > > However 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". > > Synchronous deletes are causing problems for me in production as they are > timing out in some cases. > > Thanks, > Ian > > > p.s. I'm on version 5.0.0 > -- Anshum Gupta
