You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alper Tekinalp (JIRA)" <ji...@apache.org> on 2016/05/01 21:46:12 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=15265909#comment-15265909 ] 

Alper Tekinalp commented on IGNITE-2394:
----------------------------------------

Is there any updates on that?

> 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.0.final
>            Reporter: Denis Magda
>            Assignee: Alper Tekinalp
>            Priority: Critical
>              Labels: newbie
>             Fix For: 1.6
>
>         Attachments: LocalLoadTest.java, master_186c860_IGNITE-2394.patch, master_baa1312_IGNITE-2394.patch
>
>
> 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)