[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207599#comment-16207599
]
ASF GitHub Bot commented on IGNITE-2766:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2870
IGNITE-2766 Deterministically reopen cache after client reconnect.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2766ex
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2870.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 #2870
----
commit 843566b74b3afdf78d3ede1a46adc927878c89e2
Author: Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Date: 2017-10-17T12:53:05Z
IGNITE-2766 Deterministically reopen cache after client reconnect bis.
----
> Cache instance is closed when client disconnects
> ------------------------------------------------
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
> Assignee: Ilya Kasnacheev
>
> In case client disconnects and reconnects after network timeout (i.e., with a
> new ID), all cache instances acquired by this client are closed and are not
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
