You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2016/12/28 09:49:58 UTC

[jira] [Commented] (IGNITE-3357) getOrCreateCache on second node fails replication if first node is doing loadCache

    [ https://issues.apache.org/jira/browse/IGNITE-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782526#comment-15782526 ] 

Alexey Goncharuk commented on IGNITE-3357:
------------------------------------------

[~dmagda], at the first glance the correct solution will be to restart the whole loadCache() operation. It was designed to run on a stable topology, and I am not sure if we can do something else to make sure it works correctly other than restart. The solution suggested by Kristian to use DataStreamer looks good enough to me.

> getOrCreateCache on second node fails replication if first node is doing loadCache
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-3357
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3357
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.6, 1.7
>            Reporter: Kristian Rosenvold
>            Assignee: Alexey Goncharuk
>              Labels: community, important
>
> If the first node on a REPLICATED cache is doing loadCache, a subsequent node that starts while this operation is in process will not reach identical state as the first node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)