Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 4 Aug 2016 05:51:20 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12914887.1448034797000.220505.1470289880486@Atlassian.JIRA>
In-Reply-To: <JIRA.12914887.1448034797000@Atlassian.JIRA>
References: <JIRA.12914887.1448034797000@Atlassian.JIRA> <JIRA.12914887.1448034797839@arcas>
Subject: [jira] [Commented] (IGNITE-1977) IgniteSemaphore's failover related
 tests lead to the deadlock or fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 Aug 2016 05:51:22 -0000


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

Vladimir Ozerov commented on IGNITE-1977:
-----------------------------------------

Looks like this ticket was incorrectly assigned to me. Vladislav, I re-assigned it to you because it looks like you are currently working on it. Please correct me if I wrong.

> IgniteSemaphore's failover related tests lead to the deadlock or fail
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-1977
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1977
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>            Assignee: Vladisav Jelisavcic
>
> All {{IgniteSemaphore}} related tests from {{GridCacheAbstractDataStructuresFailoverSelfTest}} may cause a deadlock which leads to the whole suite hanging.
> The threads are waiting for the following condition:
> {noformat}
> "topology-change-thread-3" prio=6 tid=0x000000001d98d800 nid=0x2b20 waiting on condition [0x000000002066f000]
>    java.lang.Thread.State: WAITING (parking)
> 	at sun.misc.Unsafe.park(Native Method)
> 	- parking to wait for  <0x0000000798149948> (a org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl$Sync)
> 	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> 	at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> 	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> 	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> 	at org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.acquire(GridCacheSemaphoreImpl.java:538)
> 	at org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.acquire(GridCacheSemaphoreImpl.java:525)
> 	at org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$7.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:571)
> 	at org.apache.ignite.internal.util.lang.GridAbsClosure.run(GridAbsClosure.java:50)
> 	at org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:967)
> 	at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
> Probably the semaphore is not properly released when a node leaves the topology abruptly.
> In addition the tests should be rewritten to the way which is followed by other data structures and atomics from this suite: using {{ConstantTopologyChangeWorker}} and its descendants.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)