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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-3357:
----------------------------------------

GitHub user krosenvold opened a pull request:

    https://github.com/apache/ignite/pull/824

    IGNITE-3357 replication failure if first node is doing loadCache

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/krosenvold/ignite IGNITE-3357

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/824.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 #824
    
----
commit 4585dc547b72d12f5b94a094937596dfbd369a43
Author: Kristian Rosenvold <kr...@apache.org>
Date:   2016-06-16T20:17:29Z

    IGNITE-3357 replikcation failure if first node is doing loadCache

----


> 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
>
> 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)