[
https://issues.apache.org/jira/browse/IGNITE-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535379#comment-16535379
]
ASF GitHub Bot commented on IGNITE-8869:
----------------------------------------
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4325
IGNITE-8869: Exclude daemon's nodes from ExchangeLatch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ivandasch/ignite ignite-8869-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4325.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 #4325
----
commit b9f0494e13159bd200bc305ddb793fd97ff41bd6
Author: Ivan Daschinskiy <ivandasch@...>
Date: 2018-07-06T21:34:02Z
IGNITE-8869: Exclude daemon's nodes from ExchangeLatch.
----
> PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on TeamCity
> ------------------------------------------------------------------
>
> Key: IGNITE-8869
> URL: https://issues.apache.org/jira/browse/IGNITE-8869
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Daschinskiy
> Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> After introduction of ExhangeLatches,
> PartitionsExchangeOnDiscoveryHistoryOverflowTest will hangs permanently. In
> current implementation, ExchangeLatchManager retrieves alive nodes from
> discoveryCache with specific affinity topology version and fails because of a
> too short discovery history. This causes fail of exchange-worker and
> therefore NoOpFailureHandler leaves node in hanging state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
