[
https://issues.apache.org/jira/browse/SOLR-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885048#comment-17885048
]
Jason Gerlowski commented on SOLR-6122:
---------------------------------------
I think I agree that canceling "core-level" actions already in-progress would
be difficult without per-node infrastructure for tracking etc. quite different
from what's there today.
And I definitely agree that limiting "cancelling" to certain types of tasks
makes sense. (Backups should be relatively "easy" IMO as they don't involve
any clusterstate changes, and Solr already [has an API that
supports|https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#deletebackup]
"garbage collecting" any orphaned or unused files out of the backup
repository)
I'm less sure what you mean by "high level cancel from Overseer". Are you
suggesting that Solr only supports canceling tasks that the overseer hasn't
started on yet at all? Or are you suggesting that Solr could also support
canceling tasks that the overseer might be in the middle of processing?
> 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
