[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332958#comment-16332958
]
Valentin Kulichenko commented on IGNITE-2766:
---------------------------------------------
[~ilyak], I believe that if cache with corresponding name still exists after
restart (either because it's configured statically on server startup, or
because persistence is used), proxy should continue to provide access to this
cache. Configuration will be changed rarely in this case, but even if it does
change, I don't see much harm. If there are any specific scenarios that would
not work properly with this approach, can you please share them?
If cache doesn't exist after restart, exception is obviously correct behavior,
although the message should be more clear I think.
> 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)
