[ https://issues.apache.org/jira/browse/IGNITE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624707#comment-15624707 ]
Vladisav Jelisavcic commented on IGNITE-637: -------------------------------------------- Unfortunately, I was rather busy lately, and I don't believe I can make it on time for this release, so I would rather leave it for the Ignite 1.9. (I'll try to finish it ASAP) > Implement IgniteReentrantReadWriteLock data structure > ----------------------------------------------------- > > Key: IGNITE-637 > URL: https://issues.apache.org/jira/browse/IGNITE-637 > Project: Ignite > Issue Type: Sub-task > Components: data structures > Reporter: Dmitriy Setrakyan > Assignee: Vladisav Jelisavcic > > We need to add {{IgniteReentrantReadWriteLock}} data structure in addition to > other data structures provided by Ignite. {{IgniteReentrantReadWriteLock}} > should have similar API to > {{java.util.concurrent.locks.ReentrantReadWriteLock}} 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 number of > readers and writers and allow user threads to block whenever needed to wait > for a lock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)