Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 16 Oct 2012 18:19:06 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <1972826430.52849.1350411546605.JavaMail.jiratomcat@arcas>
In-Reply-To: <1686392618.117854.1343681974497.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (MAPREDUCE-4495) Workflow Application Master in
 YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy commented on MAPREDUCE-4495:
------------------------------------------

bq. As we agreed before, the idea was do discuss/review the design doc (& patch if avail) before deciding on the home for this.

My understanding was that we could discuss things in the context of a specific proposal - which we now have. We also all seem to agree we need a home for this. I'd recommend we decide on the home now and get the community to discuss the proposal, having the MR community debate this would be unfair on the new community.

----

Alejandro - you mentioned on Friday (at YARN meetup) that you were considering moving this to Oozie (which makes sense to me). Are you still planning on doing so? If so, let's move the issue to Oozie project. That would be a better place to discuss. Thanks.
                
> Workflow Application Master in YARN
> -----------------------------------
>
>                 Key: MAPREDUCE-4495
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4495
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>    Affects Versions: 2.0.0-alpha
>            Reporter: Bo Wang
>            Assignee: Bo Wang
>         Attachments: MAPREDUCE-4495-v1.1.patch, MAPREDUCE-4495-v1.patch, MapReduceWorkflowAM.pdf, yapp_proposal.txt
>
>
> It is useful to have a workflow application master, which will be capable of running a DAG of jobs. The workflow client submits a DAG request to the AM and then the AM will manage the life cycle of this application in terms of requesting the needed resources from the RM, and starting, monitoring and retrying the application's individual tasks.
> Compared to running Oozie with the current MapReduce Application Master, these are some of the advantages:
>  - Less number of consumed resources, since only one application master will be spawned for the whole workflow.
>  - Reuse of resources, since the same resources can be used by multiple consecutive jobs in the workflow (no need to request/wait for resources for every individual job from the central RM).
>  - More optimization opportunities in terms of collective resource requests.
>  - Optimization opportunities in terms of rewriting and composing jobs in the workflow (e.g. pushing down Mappers).
>  - This Application Master can be reused/extended by higher systems like Pig and hive to provide an optimized way of running their workflows.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira