[ https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334403#comment-16334403 ]
ASF GitHub Bot commented on IGNITE-2766: ---------------------------------------- GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3417 IGNITE-2766 Opportunistically 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-2766 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3417.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 #3417 ---- commit a70620ca6398ba151541b5ff92c7f941eea07527 Author: Ilya Kasnacheev <ilya.kasnacheev@...> Date: 2018-01-22T15:29:36Z IGNITE-2766 Opportunistically reopen cache after client reconnect. ---- > 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 > Priority: Major > > 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 (v7.6.3#76005)