You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2016/01/15 22:32:39 UTC
[jira] [Commented] (IGNITE-2394) Cache loading from storage is
called on client nodes
[ https://issues.apache.org/jira/browse/IGNITE-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102489#comment-15102489 ]
Valentin Kulichenko commented on IGNITE-2394:
---------------------------------------------
Described solution will break data loading for local cache created on client (test attached). I think we should treat local cache as a special case and just invoke the {{CacheStore}} only locally, regardless of whether it's a server or client.
> Cache loading from storage is called on client nodes
> ----------------------------------------------------
>
> Key: IGNITE-2394
> URL: https://issues.apache.org/jira/browse/IGNITE-2394
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Denis Magda
> Priority: Critical
> Labels: newbie
> Fix For: 1.6
>
> Attachments: LocalLoadTest.java
>
>
> If to call cache.loadCache(...) then the loading from a storage will happen on all the nodes including client nodes.
> However, client nodes must be filtered out.
> If to be more precise at least this place of the code has to be modified
> {noformat}
> IgniteInternalFuture<?> globalLoadCacheAsync(@Nullable IgniteBiPredicate<K, V> p, @Nullable Object... args)
> throws IgniteCheckedException {
> ClusterGroup nodes = ctx.kernalContext().grid().cluster().forCacheNodes(ctx.name());
> {noformat}
> where forDataNodes() has to be used instead of forCacheNodes().
> Also additional tests have to be added.
> Discussion on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Loadcache-behavior-tp2571.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)