[
https://issues.apache.org/jira/browse/OOZIE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946901#comment-13946901
]
Mona Chitnis commented on OOZIE-1067:
-------------------------------------
Since this seems to be a popular ask we can target it for 4.1. However that is
subject to adequate testing resources.
> Support Amazon EMR action executor in oozie installed on EC2
> ------------------------------------------------------------
>
> Key: OOZIE-1067
> URL: https://issues.apache.org/jira/browse/OOZIE-1067
> Project: Oozie
> Issue Type: New Feature
> Components: action, coordinator, workflow
> Affects Versions: trunk
> Environment: Oozie, Amazon EMR availability, EC2 instance, access to
> Amazon S3 or S3N filesystem.
> Reporter: Shaik Idris Ali
> Priority: Critical
> Labels: Amazon, EC2, EMR, s3
> Fix For: trunk
>
> Original Estimate: 506h
> Remaining Estimate: 506h
>
> Oozie is being adopted as default workflow/scheduling engine for BigData.
> Currently, small organizations prefer on demand clusters like Amazon's EMR
> instead of full fledged Hadoop setup. However, currently we don't have
> support for powerful workflow engine like oozie, which seamlessly
> schedules/executes user jobs on EMR.
> Oozie can provide a new ActionExecutor class like EMRActionExecutor, which
> can take all the required credentials for EMR.
> Oozie can be installed on Amazon EC2 instance, which can then talk to any
> dynamic EMR cluster.
> Though, Oozie has support for other filesystems other than HDFS, we might
> need to tweak a bit to support Filesystems like S3.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
