[
https://issues.apache.org/jira/browse/SOLR-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886253#comment-17886253
]
Yuntong Qu commented on SOLR-6122:
----------------------------------
To allow cancel submitted and not started task with later on support to cancel
certain running task. We should only let overseer to decide what to remove in
its work queue.
Within the scope of using overseer:
- I propose that we have a new queue (/overseer/collection-queue-work) on ZK.
Each node can submit to cancel queue with async id they intended to cancel
through CollectionsHandler.
- On overseer (OverseerTaskProcessor), during each
[run()|https://github.com/apache/solr/blob/383d21bac694d17ae64ddae5af30cfb9b5a0c615/solr/core/src/java/org/apache/solr/cloud/OverseerTaskProcessor.java#L168],
we compare queued task from work queue with cancel queue first to cancel any
not started task, right after
[clenUpWorkQueue()|https://github.com/apache/solr/blob/383d21bac694d17ae64ddae5af30cfb9b5a0c615/solr/core/src/java/org/apache/solr/cloud/OverseerTaskProcessor.java#L245]
> 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
