[
https://issues.apache.org/jira/browse/IGNITE-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078063#comment-16078063
]
ASF GitHub Bot commented on IGNITE-5718:
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2260
IGNITE-5718: Forcible node drop makes cluster instable in some cases.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5718
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2260.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 #2260
commit 5574c14d166173b73f2892ca1228e3c2da194238
Author: Andrey V. Mashenkov
Date: 2017-07-07T13:01:44Z
Forcible node drop makes cluster unstable in some cases. Disable forcible
node drop by default.
commit 0729eb909db9ea4d253e32f79aba95597f6e1016
Author: Andrey V. Mashenkov
Date: 2017-07-07T13:02:21Z
Fix tests.
> Forcible node drop makes cluster instable in some cases.
>
>
> Key: IGNITE-5718
> URL: https://issues.apache.org/jira/browse/IGNITE-5718
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
> Fix For: 2.2
>
>
> Communication SPI can drop nodes from topology due to short network issues
> regardless failureDetectionTimout.
> Also, we throw IgniteCheckedExcpetion in safeHandshake method without any
> retry
> if remote node close connection (possibly by timeout) due to short network
> issues.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)