You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (JIRA)" <ji...@apache.org> on 2018/04/17 17:24:00 UTC

[jira] [Comment Edited] (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=16441208#comment-16441208 ] 

Maxim Muzafarov edited comment on IGNITE-2766 at 4/17/18 5:23 PM:
------------------------------------------------------------------

[~ilyak], [~dpavlov]

Due to changes of this issue, we've broked muted flaky test. I've created JIRA for fixing it.
 Please, see my changes an PR with my small fix
 https://issues.apache.org/jira/browse/IGNITE-8301


was (Author: mmuzaf):
[~ilyak], [~dpavlov]

Due to changes of this issue, we've broked muted test. I've created JIRA for fixing it.
 Please, see my changes an PR with my small fix
 https://issues.apache.org/jira/browse/IGNITE-8301

> 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
>             Fix For: 2.5
>
>
> 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)