You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (JIRA)" <ji...@apache.org> on 2018/06/14 13:25:00 UTC
[jira] [Created] (IGNITE-8796) Client node is terminated by the
Failure handler in case of dynamic cache start failed on that client node.
Vyacheslav Koptilin created IGNITE-8796:
-------------------------------------------
Summary: Client node is terminated by the Failure handler in case of dynamic cache start failed on that client node.
Key: IGNITE-8796
URL: https://issues.apache.org/jira/browse/IGNITE-8796
Project: Ignite
Issue Type: Improvement
Components: general
Affects Versions: 2.6
Reporter: Vyacheslav Koptilin
Let's consider the following scenario:
1. start a server node
2. start new client node and initiate dynamic cache start via {{Ignite.getOrCreateCache(CacheConfiguration)}} method.
3. let's assume that {{GridDhtPartitionsExchangeFuture.onCacheChangeRequest()}} results in {{Exception}} on the client node only.
4. In that case, the cache is considered as started on the server node. On the other hand, the client node is terminated by {{FailureHandler}}.
It seems that this behavior can be improved using the same approach as server nodes.
See IGNITE-1094 for the details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)