[
https://issues.apache.org/jira/browse/IGNITE-9493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726683#comment-16726683
]
ASF GitHub Bot commented on IGNITE-9493:
----------------------------------------
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/5720
IGNITE-9493 Communication error resolver shouldn`t be called on client node
failed.
…t node failed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9493
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5720.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5720
----
commit 1d24459882db72bba83bcf6a9db836c76834dbf0
Author: Evgeny Stanilovskiy <estanilovskiy@...>
Date: 2018-12-21T12:11:13Z
IGNITE-9493 Communication error resolver shouldn`t be called on client node
failed.
----
> Communication error resolver shouldn't be invoked if connection with client
> breaks unexpectedly
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-9493
> URL: https://issues.apache.org/jira/browse/IGNITE-9493
> Project: Ignite
> Issue Type: Bug
> Components: cache, zookeeper
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Assignee: Stanilovsky Evgeny
> Priority: Major
> Fix For: 2.8
>
>
> Currently, we initiate communication error resolving process even if a
> connection between server and client breaks unexpectedly.
> This is unnecessary action because client nodes are not important for cluster
> stability. We should ignore communication errors for client and daemon nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
