[ 
https://issues.apache.org/jira/browse/IGNITE-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov updated IGNITE-10819:
-------------------------------------
    Ignite Flags:   (was: Docs Required)

> Test IgniteClientRejoinTest.testClientsReconnectAfterStart became flaky in 
> master recently
> ------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10819
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10819
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> As [test 
> history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-21180267941031641&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
>  in master branch shows the test has become flaky in master recently.
> Test started failing when IGNITE-10555 was merged to master.
> The reason of failure is timeout when *client4* node hangs waiting for PME to 
> complete. Communication failures are emulated in the test and when all 
> clients fail to init an exchange on a specific affinity topology version 
> (major=7, minor=1) everything works fine.
> But sometimes *client4* node manages to finish init the exchange and hangs 
> forever.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to