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-642) Implement IgniteReentrantLock data structure
Date Thu, 09 Apr 2015 18:59:14 GMT

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

Dmitriy Setrakyan reassigned IGNITE-642:
----------------------------------------

    Assignee: Atri Sharma  (was: Dmitriy Setrakyan)

> Implement IgniteReentrantLock data structure
> --------------------------------------------
>
>                 Key: IGNITE-642
>                 URL: https://issues.apache.org/jira/browse/IGNITE-642
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: data structures
>            Reporter: Dmitriy Setrakyan
>            Assignee: Atri Sharma
>
> We need to add {{IgniteReentrantLock}} data structure in addition to other data structures
provided by Ignite. {{IgniteReentrantLock}} should have similar API to {{java.util.concurrent.locks.ReentrantLock}}
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 lock-owner identifier together
with a queue of waiters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message