You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/14 17:17:00 UTC

[jira] [Commented] (IGNITE-5452) GridTimeoutProcessor can hang on stop.

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

ASF GitHub Bot commented on IGNITE-5452:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/2279


> GridTimeoutProcessor can hang on stop.
> --------------------------------------
>
>                 Key: IGNITE-5452
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5452
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Andrew Mashenkov
>            Assignee: Vitaliy Biryukov 
>             Fix For: 2.2
>
>         Attachments: LockTimeoutFailedOnStop.java
>
>
> PFA repro attached.
> Actually, there are 2 issue.
> 1. GridTimeoutProcessor can't be stopped if TimeoutObject eats InterruptedException. We should handle this correctly.
> 2. TX use TimeoutObjects to be rolled back by timeout.  However, TXs doesn't remove their TimeoutObjects on node stop. 
> Possible, TimeoutObject doesn't removed on TX rollback and this should be investigated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)