ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2766) Cache instance is closed when client disconnects
Date Fri, 06 Oct 2017 17:22:00 GMT

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

ASF GitHub Bot commented on IGNITE-2766:

GitHub user alamar opened a pull request:


    IGNITE-2766 Essais: Opportunistic reopen cache.


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:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2816
commit 3e8d3e8d756290e749a3f2d2a1a4deba97743a26
Author: Ilya Kasnacheev <ilya.kasnacheev@gmail.com>
Date:   2017-10-06T17:19:56Z

    IGNITE-2766 Essais: Opportunistic reopen cache.


> 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

View raw message