You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/10 11:17:00 UTC

[jira] [Commented] (IGNITE-10910) GridTaskProcessor#onKernalStop may lead to a deadlock and execution timeout in "SPI" TC build-plan

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

Maxim Muzafarov commented on IGNITE-10910:
------------------------------------------

Moved to the next release due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.


> GridTaskProcessor#onKernalStop may lead to a deadlock and execution timeout in "SPI" TC build-plan
> --------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10910
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10910
>             Project: Ignite
>          Issue Type: Task
>    Affects Versions: 2.7
>            Reporter: Vyacheslav Daradur
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> In rare cases calling of {{GridTaskProcessor#onKernalStop}} may lead to a deadlock with the following stack trace:
> {code:java}
> "node-stopper" #225287 prio=5 os_prio=0 tid=0x00007f224057a800 nid=0x233aae waiting on condition [0x00007f24607ef000]
>    java.lang.Thread.State: TIMED_WAITING (sleeping)
> 	at java.lang.Thread.sleep(Native Method)
> 	at org.apache.ignite.internal.util.GridSpinReadWriteLock.tryWriteLock(GridSpinReadWriteLock.java:347)
> 	at org.apache.ignite.internal.processors.task.GridTaskProcessor.onKernalStop(GridTaskProcessor.java:198)
> 	at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2305)
> 	at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2253)
> 	at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2614)
> 	- locked <0x000000009f42a970> (a org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> 	at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2577)
> 	at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
> 	at org.apache.ignite.failure.StopNodeFailureHandler$1.run(StopNodeFailureHandler.java:36)
> 	at java.lang.Thread.run(Thread.java:748)
> {code}
> It's the cause of execution timeout of "SPI" build-plan on TC:
>  [https://ci.ignite.apache.org/viewLog.html?buildId=2698887]
>  [https://ci.ignite.apache.org/viewLog.html?buildId=2689621]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)