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

Vadim Pakhnushev resolved IGNITE-24199.
---------------------------------------
    Resolution: Duplicate

Will be fixed in IGNITE-24174

> Compute job failed over to another node is not cancelled via cancel handle
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-24199
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24199
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>            Reporter: Vadim Pakhnushev
>            Assignee: Vadim Pakhnushev
>            Priority: Major
>              Labels: ignite-3
>
> If a remote compute job is failed over to another node and it is cancelled 
> via the cancel handle, the {{CancelHandle.cancel()}} hangs indefinitely 
> waiting for the original job to cancel.
> {{ComputeComponentImpl.executeRemotely}} adds the original job's 
> {{resultAsync}} as a dependency to the {{CancelHandle}}. When the job is 
> failed over, new job is also added to this handle.
> {{ItWorkerShutdownTest#cancelRemoteExecutionOnRestartedJob}}



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

Reply via email to