You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Menshikov (JIRA)" <ji...@apache.org> on 2017/06/14 15:56:00 UTC
[jira] [Comment Edited] (IGNITE-4684) Local cache.get(K) should not
block
[ https://issues.apache.org/jira/browse/IGNITE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049282#comment-16049282 ]
Alexander Menshikov edited comment on IGNITE-4684 at 6/14/17 3:55 PM:
----------------------------------------------------------------------
[~yzhdanov]
Do you mean IgniteCacheProcessProxy or IgniteProcessProxy? Looks like the IgniteProcessProxy doesn't have any unnecessary locks. But in the IgniteCacheProcessProxy there is the readlook in IgniteComputeImpl#callAsync0 which looks unnecessary because the GridClosureProcessor.callAsync() already have busyLock inside.
was (Author: sharpler):
[~yzhdanov]
Do you mean IgniteCacheProcessProxy or IgniteProcessProxy?
> Local cache.get(K) should not block
> -----------------------------------
>
> Key: IGNITE-4684
> URL: https://issues.apache.org/jira/browse/IGNITE-4684
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Yakov Zhdanov
> Fix For: 2.1
>
>
> Currently there is synchronized section on desired cache entry which cause problems on multithreaded access
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)