[
https://issues.apache.org/jira/browse/IGNITE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470816#comment-16470816
]
Dmitriy Pavlov edited comment on IGNITE-5789 at 5/10/18 5:43 PM:
-----------------------------------------------------------------
I've queued one more TC run with actual master with this fix,
[https://ci.ignite.apache.org/viewQueued.html?itemId=1281364&tab=queuedBuildOverviewTab]
But for PR merge it is still desired to rebase/merge current branch to avoid
conflicts.
was (Author: dpavlov):
I've queued one more TC run with actual master with this fix,
[https://ci.ignite.apache.org/viewQueued.html?itemId=1281364&tab=queuedBuildOverviewTab]
But for merge it is still desired to rebase/merge to avoid conflicts.
> After client reconnects to server if server was restarted, client doesn't
> create caches defined in client's configuration
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-5789
> URL: https://issues.apache.org/jira/browse/IGNITE-5789
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Evgenii Zhuravlev
> Assignee: vk
> Priority: Major
> Fix For: 2.6
>
> Attachments: ClientReconnectAfterClusterRestartTest.java
>
>
> User with this problem on SO:
> https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
