You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/03/30 06:44:52 UTC
[jira] [Updated] (IGNITE-637) Implement
IgniteReentrantReadWriteLock data structure
[ https://issues.apache.org/jira/browse/IGNITE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Setrakyan updated IGNITE-637:
-------------------------------------
Issue Type: Sub-task (was: New Feature)
Parent: IGNITE-641
> 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
>
> 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)