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

Posted to dev@reef.apache.org by "Joo Seong (Jason) Jeong (JIRA)" <ji...@apache.org> on 2015/10/14 06:41:05 UTC

[jira] [Resolved] (REEF-830) TreeTopology does not work correctly for certain task addition orders

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

Joo Seong (Jason) Jeong resolved REEF-830.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.14

Resolved via [PR 559|https://github.com/apache/incubator-reef/pull/559].

> TreeTopology does not work correctly for certain task addition orders
> ---------------------------------------------------------------------
>
>                 Key: REEF-830
>                 URL: https://issues.apache.org/jira/browse/REEF-830
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF-IO
>            Reporter: Gyeongin Yu
>            Assignee: Gyeongin Yu
>             Fix For: 0.14
>
>
> This issue is related to [REEF-817|https://issues.apache.org/jira/browse/REEF-817]. {{TreeTopology}} does not work correctly when the root task is added later than child tasks.
> {{TreeTopology}} uses the {{prev}} field to track the lastly added leaf without considering that the root task might not be present yet. Thus if the root task is added later than others, {{TreeTopology.addTask}} sets {{prev}} as the root task before it exits, leading to incorrect sibling relations between nodes.
> This bug can be reproduced by doing the following:
> 1. add two child tasks
> 2. add root task
> 3. add five child tasks
> This was first found by [~chobrian].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)