[
https://issues.apache.org/jira/browse/SOLR-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887753#comment-17887753
]
David Smiley commented on SOLR-6122:
------------------------------------
I see this is for "submitted not started". Coincidentally at work (Salesforce)
we have an Overseer customization but it's scoped to a synchronous use-case and
only when the caller has gone/vanished. Any way, for async, I think this is
simpler. DELETESTATUS is documented to only succeed for completed tasks. But
I could imagine adding a parameter to cancel a not-started status. Can you
look into this? I suppose this might be viewed as very similar to your listed
Approach #2. Honestly I don't think your listed "Cons" for it is a is a big
concern. To make it a little better, you could put the relevant logic for the
details of that in OverseerTaskProcessor or other similar place close to the
queue logic and not in the command you will write.
BTW I really appreciate your open development process here, even if it takes
longer. It's good to solicit early feedback from others who have been in and
out of this code a lot. Often times I see a PR before a discussion of the
approach :-/
> API to cancel an already submitted/running Collections API call
> ---------------------------------------------------------------
>
> Key: SOLR-6122
> URL: https://issues.apache.org/jira/browse/SOLR-6122
> Project: Solr
> Issue Type: Wish
> Components: SolrCloud
> Reporter: Anshum Gupta
> Priority: Major
>
> Right now we can trigger a long running task with no way to cancel it
> cleanly.
> We should have an API that interrupts the already running/submitted
> collections API call.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
