[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470246#comment-16470246 ] Alexey Kuznetsov commented on IGNITE-9: --- [~avinogradov] Yeah, if IgniteReentrantLock2 would be created in any case, then we can implement IngniteReentrantReadWriteLock now > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Priority: Major > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470232#comment-16470232 ] Anton Vinogradov commented on IGNITE-9: --- [~Alexey Kuznetsov], Anyway reworked case will cause IgniteReentrantLock2 creation. IgniteReentrantLock still will be workable. Any real reason to wait such rework? > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Priority: Major > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470073#comment-16470073 ] Alexey Kuznetsov commented on IGNITE-9: --- [~avinogradov] Current implementation of IngniteReentrantReadWriteLock heavily relies on IngniteReentrantLock. I still believe it would rely on IgniteReentrantLock in future. > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Priority: Major > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422747#comment-16422747 ] Anton Vinogradov commented on IGNITE-9: --- I think there is no need to wait for new implementation We have to implement IngniteReentrantReadWriteLock using current implementation. > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Priority: Major > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422119#comment-16422119 ] Alexey Kuznetsov commented on IGNITE-9: --- Start after IgniteReentrantLock is implemented : https://issues.apache.org/jira/browse/IGNITE-4908 > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Priority: Major > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119973#comment-16119973 ] Alexey Kuznetsov commented on IGNITE-9: --- 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. > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Alexey Kuznetsov > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118120#comment-16118120 ] Alexey Kuznetsov commented on IGNITE-9: --- [~yzhdanov] Currently, as it implemented at *GridCacheLockImpl* when one node waits on condition, signal (on condition with the same name, with the same lock) from another node cannot awake it. Only signal from the same node works. Should we provide the same behavior for *IngniteReentrantReadWriteLock*, for read lock and write lock ? Why do we need to provide name when creating condition in org.apache.ignite.IgniteLock#getOrCreateCondition()?(As conditions from different nodes seems not to be connected) > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Alexey Kuznetsov > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-9) Need to implement IngniteReentrantReadWriteLock
[ https://issues.apache.org/jira/browse/IGNITE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094438#comment-16094438 ] Alexey Kuznetsov commented on IGNITE-9: --- [~yzhdanov] I m going to start posting here a list of new methods for the lock, that absent in jdk reentrant read write lock. > Need to implement IngniteReentrantReadWriteLock > --- > > Key: IGNITE-9 > URL: https://issues.apache.org/jira/browse/IGNITE-9 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Alexey Kuznetsov > > See org.apache.ignite.IgniteLock for reference -- This message was sent by Atlassian JIRA (v6.4.14#64029)