ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-637) Implement IgniteReentrantReadWriteLock data structure
Date Wed, 08 Apr 2015 19:56:14 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dmitriy Setrakyan reassigned IGNITE-637:

    Assignee: Dmitriy Setrakyan

> 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: 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]
> 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

View raw message