[ 
https://issues.apache.org/jira/browse/IGNITE-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537567#comment-16537567
 ] 

ASF GitHub Bot commented on IGNITE-8869:
----------------------------------------

GitHub user ivandasch opened a pull request:

    https://github.com/apache/ignite/pull/4337

    IGNITE-8869: cancel patch

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8869-revert

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4337.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 #4337
    
----
commit ce131f5a129197b8137310be7d1633e7f2a3727e
Author: Ivan Daschinskiy <ivandasch@...>
Date:   2018-07-09T20:57:51Z

    IGNITE-8869: cancel patch

----


> 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)

Reply via email to