GitHub user dmagda opened a pull request:
https://github.com/apache/incubator-ignite/pull/19 ignite-1241-dev: fixed failure timeout warning when only client is connected
This warning is printed out when a local server node is considered to be disconnected from the ring - it neither receives message nor sends to the next node.
In the buggy configuration (one server and one client nodes) the server periodically received messages from the client node but unable to send connection check messages to the next node cause there was no any. This affected failure detection timeout implementation logic.
As a fix, the failure should be detected and reported only when there are remote server nodes in a topology and a local node seems to be disconnected from them. To support this "TcpDiscovery.hasRemoteServerNodes()" method was implemented and used by failure timeout logic.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/dmagda/incubator-ignite ignite-1241-dev
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-ignite/pull/19.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #19
----
commit 38070b28bdda9e95b125f27706037c9916edeeb6
Author: Denis Magda <
[hidden email]>
Date: 2015-08-14T13:20:18Z
ignite-1241-dev: fixed endless "failure detection threshold" warnings for the case when there is only one server and client nodes in the topology
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at
[hidden email] or file a JIRA ticket
with INFRA.
---
Locked
