reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1507) IMap and IUpdate tasks should be initialized in the *Host constructors
Date Tue, 29 Nov 2016 02:53:59 GMT

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

Julia commented on REEF-1507:
-----------------------------

We have moved waiting for registration out of the task host constructor. We would like to
move the data materialization out of the task constructor as well in stead of just at the
end of the constructor.   Is the Jira for that purpose? 

> IMap and IUpdate tasks should be initialized in the *Host constructors
> ----------------------------------------------------------------------
>
>                 Key: REEF-1507
>                 URL: https://issues.apache.org/jira/browse/REEF-1507
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET
>         Environment: C#
>            Reporter: Dhruv Mahajan
>            Assignee: Dhruv Mahajan
>
> Currently in IMRU, {{IMapTask}} and {{IUpdateTask}} are injected as part of constructor
of corresponding {{*Host}} Tasks. As a result currently, when we ask for group comm. operators
and registration happens, first we have to wait for data to be downloaded, since it is typically
accessed within the constructor of {{IMapTask}}. As a result master task can timeout in registration
and retry parameter there needs to change depending on the size of data. 
> We would like to delay the initiation of {{IMapTask}} by getting the injector in the
task creation and only initiating the map and master tasks at the end of the constructor.



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

Mime
View raw message