[
https://issues.apache.org/jira/browse/IGNITE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623725#comment-15623725
]
Denis Magda commented on IGNITE-637:
------------------------------------
[~vladisav], are you planning to complete this feature in the nearest time? In
the middle of November we're planning to release Ignite 1.8 and it will be
great to have this feature in the release.
> 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)
