[ https://issues.apache.org/jira/browse/IGNITE-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546540#comment-16546540 ]
Alexey Goncharuk commented on IGNITE-8783: ------------------------------------------ [~avinogradov], Currently your change never completes the client latch because {{coordinator}} is a {{ClusterNode}}, but {{nodeIds}} is a {{Set<UUID>}}. Can you please clarify why you need to check for coordinator? > Failover tests periodically cause hanging of the whole Data Structures suite > on TC > ---------------------------------------------------------------------------------- > > Key: IGNITE-8783 > URL: https://issues.apache.org/jira/browse/IGNITE-8783 > Project: Ignite > Issue Type: Bug > Components: data structures > Reporter: Ivan Rakov > Assignee: Anton Vinogradov > Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > History of suite runs: > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E > Chance of suite hang is 18% in master (based on previous 50 runs). > Hang is always caused by one of the following failover tests: > {noformat} > GridCacheReplicatedDataStructuresFailoverSelfTest#testAtomicSequenceConstantTopologyChange > GridCachePartitionedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)