You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (JIRA)" <ji...@apache.org> on 2018/05/22 11:42:00 UTC

[jira] [Updated] (IGNITE-6538) Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC

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

Maxim Muzafarov updated IGNITE-6538:
------------------------------------
    Description: 
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=-238119157387028099&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E

{code}
[14:36:09]W:		 [org.apache.ignite:ignite-core] [2018-05-22 11:36:09,817][WARN ][exchange-worker-#202059%node1-backUp%][GridDhtPartitionsExchangeFuture] Unable to await partitions release latch within timeout: ClientLatch [coordinator=TcpDiscoveryNode [id=ba7f90d8-3a1f-488a-a8ea-3ae2fdf016fe, addrs=[127.0.0.1, 172.17.0.7], sockAddrs=[/127.0.0.1:47503, d377975c5791/172.17.0.7:47503], discPort=47503, order=1, intOrder=1, lastExchangeTime=1526985998704, loc=false, ver=2.5.0#20180522-sha1:d37470c7, isClient=false], ackSent=true, super=CompletableLatch [id=exchange, topVer=AffinityTopologyVersion [topVer=6, minorTopVer=1]]]
{code}

Fail test:
{code}
org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
{code}


  was:
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=-238119157387028099&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E

recent changes from [IGNITE-6124] which probably showed this problem is following 
{noformat}
 fail("Activation should fail");
{noformat}
org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock

Locally fail can be also reproduced, 6 from 20 failures.


> Ignite Activate/Deactivate Cluster suite: After tests validation improvements test became flaky on TC
> -----------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6538
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6538
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 2.1
>            Reporter: Dmitriy Pavlov
>            Assignee: Maxim Muzafarov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, Muted_test
>             Fix For: 2.6
>
>
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=-238119157387028099&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E
> {code}
> [14:36:09]W:		 [org.apache.ignite:ignite-core] [2018-05-22 11:36:09,817][WARN ][exchange-worker-#202059%node1-backUp%][GridDhtPartitionsExchangeFuture] Unable to await partitions release latch within timeout: ClientLatch [coordinator=TcpDiscoveryNode [id=ba7f90d8-3a1f-488a-a8ea-3ae2fdf016fe, addrs=[127.0.0.1, 172.17.0.7], sockAddrs=[/127.0.0.1:47503, d377975c5791/172.17.0.7:47503], discPort=47503, order=1, intOrder=1, lastExchangeTime=1526985998704, loc=false, ver=2.5.0#20180522-sha1:d37470c7, isClient=false], ackSent=true, super=CompletableLatch [id=exchange, topVer=AffinityTopologyVersion [topVer=6, minorTopVer=1]]]
> {code}
> Fail test:
> {code}
> org.apache.ignite.internal.processors.cache.persistence.standbycluster.IgniteChangeGlobalStateTest#testActivateAfterFailGetLock
> {code}



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