[jira] [Commented] (IGNITE-16916) Make nodes more resilient in case of a job cancellation

["Pavel Pereslegin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600322#comment-17600322 ] 

Pavel Pereslegin commented on IGNITE-16916:
-------------------------------------------

[~ktkalenko@gridgain.com], 

could you please suggest any workaround for system/internal tasks to cancel them immediately without changing 'computeJobWorkerInterruptTimeout' property?

> Make nodes more resilient in case of a job cancellation
> -------------------------------------------------------
>
>                 Key: IGNITE-16916
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16916
>             Project: Ignite
>          Issue Type: Task
>          Components: compute
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>             Fix For: 2.14
>
>         Attachments: image-2022-05-05-12-46-26-543.png, screenshot-1.png
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In case of a job being cancelled we currently have a really questionable approach.
> We are now setting the interruption flag even before we give a use a chance to stop the job gracefully.
> Proposal for the implementation:
> * Adding a distributed property in the metastore that will set a timeout for interrupting *GridJobWorker* that did not gracefully complete after calling *GridJobWorker#cancel*;
> * On the call of the *GridJobWorker#cancel*, do not *Thread#interrupt* the thread, but add *GridTimeoutObject*.



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