[
https://issues.apache.org/jira/browse/IGNITE-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161320#comment-16161320
]
ASF GitHub Bot commented on IGNITE-6340:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2635
IGNITE-6340 : Fixed creation of client cache on server node.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6340
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2635.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2635
----
commit 8b6f7dfe5b87154c77cd782be2597df2248700df
Author: Ilya Lantukh <[email protected]>
Date: 2017-09-11T14:07:43Z
ignite-6340 : Fixed creation of client cache on server node.
commit 4852c80d095767d94326ce8f894541ea8ecb85ee
Author: Ilya Lantukh <[email protected]>
Date: 2017-09-11T14:14:50Z
ignite-6340 : fixed code style.
----
> Attempt to create the same cache from multiple threads leads to creation of
> client cache on server node
> -------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-6340
> URL: https://issues.apache.org/jira/browse/IGNITE-6340
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.1
> Reporter: Ilya Lantukh
> Assignee: Ilya Lantukh
>
> Implementation of GridCacheProcessor.prepareCacheChangeRequest(...) is based
> on assumption that if CacheDescriptor exists on affinity node, than server
> cache also exists. However, this invariant is invalid in general case. For
> example, request to create cache for given descriptor might be already in
> queue but still unprocessed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
