[jira] [Commented] (IGNITE-637) Implement IgniteReentrantReadWriteLock data structure

["Atri Sharma (JIRA)" <ji...@apache.org>]

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

Atri Sharma commented on IGNITE-637:
------------------------------------

I see no update on this as yet.

Since I am working on IGNITE 642 anyways, I can take this up as well.

Assigning to myself for now. Please let me know if changes are needed.

> 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: Sergey Eliseev
>
> 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)