ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8869) PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on TeamCity
Date Tue, 26 Jun 2018 15:13:00 GMT

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

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

GitHub user ivandasch opened a pull request:

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

    IGNITE-8869: Explicitly fail hanging test.

    

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

    $ git pull https://github.com/ivandasch/ignite ignite-8869

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

    https://github.com/apache/ignite/pull/4260.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 #4260
    
----
commit 50034302a6ac9ac38a5f347b6f26b0b43715eb39
Author: Ivan Daschinskiy <ivandasch@...>
Date:   2018-06-26T15:10:58Z

    IGNITE-8869: Explicitly fail hanging test.

----


> 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
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.6
>
>
> 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)

Mime
View raw message