[ https://issues.apache.org/jira/browse/IGNITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261814#comment-15261814 ]
ASF GitHub Bot commented on IGNITE-642: --------------------------------------- Github user vladisav closed the pull request at: https://github.com/apache/ignite/pull/519 > Implement IgniteReentrantLock data structure > -------------------------------------------- > > Key: IGNITE-642 > URL: https://issues.apache.org/jira/browse/IGNITE-642 > Project: Ignite > Issue Type: Sub-task > Components: data structures > Affects Versions: 1.6 > Reporter: Dmitriy Setrakyan > Assignee: Vladisav Jelisavcic > Labels: features > Fix For: 1.6 > > > We need to add {{IgniteReentrantLock}} data structure in addition to other > data structures provided by Ignite. {{IgniteReentrantLock}} should have > similar API to {{java.util.concurrent.locks.ReentrantLock}} class in JDK. > As an example, you can see how > [IgniteCountDownLatch|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteCountDownLatch.java] > is implemented in > [GridCacheCountDownLatchImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridCacheCountDownLatchImpl.java] > class. > In general we need to have an entity in ATOMIC cache storing lock-owner > identifier together with a queue of waiters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)