[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332032#comment-16332032
]
Ilya Kasnacheev commented on IGNITE-2766:
-----------------------------------------
"Client node was reconnected after it was already considered failed by the
server topology (this could happen after all servers restarted or due to a long
network outage between the client and servers). All continuous queries and
remote event listeners created by this client will be unsubscribed, consider
listening to EVT_CLIENT_NODE_RECONNECTED event to restore them."
I guess that means cache proxies are no longer good either.
> 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)
