You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/08/30 15:32:00 UTC

[jira] [Updated] (IGNITE-9436) Compute task may cause a deadlock on node stop.

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

Andrew Mashenkov updated IGNITE-9436:
-------------------------------------
    Labels: MakeTeamcityGreenAgain  (was: )

> Compute task may cause a deadlock on node stop.
> -----------------------------------------------
>
>                 Key: IGNITE-9436
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9436
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>            Reporter: Andrew Mashenkov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>
> Task that is waiting for async compute call result on reduce may lead to deadlock on node stop.
> This task will hold GridTaskProcessor.readlock and waits for remote call result on future.
> At that time node stopping thread will try to acquire GridTaskProcessor.writeLock.
> GridTaskProcessor job message listener will try to acquire GridTaskProcessor.readLock with no success.
> So, grid can't be stopped as there is a task on fly, but remote call result also can't be delivered to task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)