You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/04/12 10:56:00 UTC

[jira] [Commented] (IGNITE-11732) Multi-merged partitions exchange future may hang if node left event is received last

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

Ignite TC Bot commented on IGNITE-11732:
----------------------------------------

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Scala (Visor Console){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3578862]]

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3573028&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Multi-merged partitions exchange future may hang if node left event is received last
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11732
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11732
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The scenario is similar to IGNITE-11204, but several exchanges should be merged. If in this case a merged-exchange node is left and all other nodes messages are already received, the exchange will not be completed because {{F.isEmpty(mergedJoinExchMsgs)}} is {{false}}. 
> Looks like we should decrement the {{awaitMergedMsgs}} and check this field for {{0}}.



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