[
https://issues.apache.org/jira/browse/IGNITE-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532729#comment-17532729
]
Ignite TC Bot commented on IGNITE-16916:
----------------------------------------
{panel:title=Branch: [pull/10015/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10015/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6558164&buildTypeId=IgniteTests24Java8_RunAll]
> 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: 0.5h
> 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.7#820007)
