[
https://issues.apache.org/jira/browse/IGNITE-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102005#comment-16102005
]
Valentin Kulichenko commented on IGNITE-5838:
---------------------------------------------
[~liyuj]
I reproduced the behavior, but I really doubt this is blocker, so I lowered the
priority.
First of all, there is always an easy workaround - just call synchronous method
in a separate thread to get pure async behavior. Second of all, this happens
only for a scenario when {{loadCache}} is called on a server node. If you call
it from the client, it will not wait for any network operations.
Having said that, this is driven by current semantics of asynchronous internal
operations. However, I agree that it makes sense to change this behavior for
cache loading, as it's generally a long process. If it's important for you,
feel free to assign ticket to yourself and contribute. If you have any question
- welcome to the dev mailing list.
> The IgniteCache.loadCacheAsync method is not executed asynchronously.
> ---------------------------------------------------------------------
>
> Key: IGNITE-5838
> URL: https://issues.apache.org/jira/browse/IGNITE-5838
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.0
> Reporter: Yujue Li
> Fix For: 2.2
>
>
> The IgniteCache.loadCacheAsync method is not executed asynchronously.
> for example,in the
> https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store/spring/CacheSpringStoreExample.java:
> line 129:
> If modified to:
> cache.loadCacheAsync(null, ENTRY_COUNT);
> We will find that the cache is not loaded asynchronously.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
