You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2024/11/22 14:51:00 UTC

[jira] [Assigned] (IGNITE-23440) Provide internal API for external components to register itself as cancellation listener

     [ https://issues.apache.org/jira/browse/IGNITE-23440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Pereslegin reassigned IGNITE-23440:
-----------------------------------------

    Assignee: Pavel Pereslegin

> Provide internal API for external components to register itself as cancellation listener
> ----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-23440
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23440
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Pavel Pereslegin
>            Assignee: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> At the moment we have 3 types of cancelable "activities".
> # SQL query
> # Transaction
> # Compute job
> Any of these process can be cancelled (killed) using SQL KILL query.
> We need to design and implement a handler (KillQueryHandler?) that will add the ability for external components (TransactionManager, IgniteComputeImpl, etc) to register as a cancellation listener.
> Overall, the cancellation of any such "process" consists of the following steps:
> * if the process is local - cancel it
> * send a message to other cluster nodes to cancel the process
> Note: {{IgniteCompute}} already has a {{cancelAsync}} method for cancelling compute jobs (need to keep in mind how to integrate with it)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)