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 2021/04/07 18:44:00 UTC
[jira] [Assigned] (IGNITE-8796) Client node is terminated by the
Failure handler in case of dynamic cache start failed on that client node.
[ https://issues.apache.org/jira/browse/IGNITE-8796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov reassigned IGNITE-8796:
---------------------------------------
Assignee: Maxim Muzafarov
> 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
> Assignee: Maxim Muzafarov
> Priority: Major
>
> 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
(v8.3.4#803005)