You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Zhengping Qian (JIRA)" <ji...@apache.org> on 2015/07/24 19:09:05 UTC
[jira] [Commented] (REEF-500) Simple duplicate Vortex Tasklet
launch
[ https://issues.apache.org/jira/browse/REEF-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640751#comment-14640751 ]
Zhengping Qian commented on REEF-500:
-------------------------------------
FYI, a related work on the scheduling policy (with duplicate execution; for volunteer computing): http://groups.csail.mit.edu/cag/bayanihan/papers/fgcs/html/node10.html
It looks to me a simple/good one to try.
> Simple duplicate Vortex Tasklet launch
> --------------------------------------
>
> Key: REEF-500
> URL: https://issues.apache.org/jira/browse/REEF-500
> Project: REEF
> Issue Type: Sub-task
> Components: Vortex
> Reporter: John Yang
> Assignee: John Yang
>
> To proactively cope with frequent resource preemptions, we can duplicate launch Tasklets. As a first step to support this, we work on the following things:
> * Add metadata(e.g. replica info) to Tasklet
> * Keep track of duplicate Tasklets in VortexMaster
> * Introduce Tasklet priority, giving lower priority to duplicated ones compared to the original ones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)