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

["Alexey Kuznetsov (JIRA)" <ji...@apache.org>]

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

Alexey Kuznetsov commented on IGNITE-637:
-----------------------------------------

New implementation of ignite reentrant lock will be provided in https://issues.apache.org/jira/browse/IGNITE-4908
ignite reentrant read write lock should be based on this implementation.

> 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: Alexey Kuznetsov
>            Priority: Major
>
> 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
(v7.6.3#76005)