You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/21 15:06:00 UTC
[jira] [Commented] (IGNITE-2766) Cache instance is closed when
client disconnects
[ https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260872#comment-16260872 ]
ASF GitHub Bot commented on IGNITE-2766:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3077
IGNITE-2766 Ensure that cache is available after client ID changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2766test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3077.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 #3077
----
----
> 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)