[
https://issues.apache.org/jira/browse/IGNITE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382924#comment-15382924
]
Vladisav Jelisavcic commented on IGNITE-637:
--------------------------------------------
Dmitriy, Krome,
I have almost finished implementing this ticket, but unfortunately I've had a
really busy period here at my day job,
so I won't be able to wrap it up for at least a week or two (expect PR sometime
beginning of August).
In the meantime, do you think it may be useful to also add another feature in
the next release: ReadWriteUpdateLock?
See [this stackexchange post|http://codereview.stackexchange.com/a/31231] for
more info.
> 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: Vladisav Jelisavcic
>
> 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)
