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

Subru Krishnan commented on HADOOP-14840:
-----------------------------------------

[~tangshangwen], thanks for your interest. There is a follow up planned (scope 
we have defined in the documentation 
[here|http://hadoop.apache.org/docs/current/hadoop-resourceestimator/ResourceEstimator.html#Future]),
 unfortunately it won't be immediately as currently my plate is full.

Do you have any interest in picking it up?

> Tool to estimate resource requirements of an application pipeline based on 
> prior executions
> -------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-14840
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14840
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: tools
>            Reporter: Subru Krishnan
>            Assignee: Rui Li
>            Priority: Major
>             Fix For: 2.9.0, 3.0.0, 3.1.0
>
>         Attachments: HADOOP-14840-branch-2-v4.patch, HADOOP-14840-v1.patch, 
> HADOOP-14840-v2.patch, HADOOP-14840-v3.patch, HADOOP-14840-v4.patch, 
> ResourceEstimator-design-v1.pdf
>
>
> We have been working on providing SLAs for job execution on Hadoop. At high 
> level this involves 2 parts: deriving the resource requirements of a job and 
> guaranteeing the estimated resources at runtime. The {{YARN 
> ReservationSystem}} (YARN-1051/YARN-2572/YARN-5326) enable the latter and in 
> this JIRA, we propose to add a tool to Hadoop to predict the  resource 
> requirements of a job based on past executions of the job. The system (aka 
> *Morpheus*) deep dive can be found in our OSDI'16 paper 
> [here|https://www.usenix.org/conference/osdi16/technical-sessions/presentation/jyothi].



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to