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

Jaigak Song commented on MAPREDUCE-4393:
----------------------------------------

Bikas, thanks for your comments!
Regarding #1, some shell related portion and some more can be abstracted out, 
but I don't see much value out of that in my opinion.

For #2, I agree on that AM can be used, but first, #3 should be implemented 
before that in order to have one place to maintain available containers of the 
same application type. Besides, ZooKeeper seems a better choice at this point 
as the PaaS implementation has Routers (which is not part of the patch due to 
some dependency), which are supposed to distribute incoming requests by 
utilizing the information of which containers are available for which 
application type. If there are multiple AM's (e.g. hundreds or thousands of 
AM's) for different application types, ZooKeeper is much simpler to use and can 
be better performant because of its asynchronous characteristics.

For #3, I received the same suggestion from Arun Murthy a couple of weeks ago 
and I put it as an enhancement to my documentation to distribute soon. 
Certainly we can improve the application later. This implementation was a POC 
done within a couple of weeks.  
                
> PaaS on YARN: an YARN application to demonstrate that YARN can be used as a 
> PaaS
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4393
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4393
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: examples
>    Affects Versions: 0.23.1
>            Reporter: Jaigak Song
>            Assignee: Jaigak Song
>             Fix For: 3.0.0
>
>         Attachments: HADOOPasPAAS_Architecture.pdf, MAPREDUCE-4393.patch, 
> MAPREDUCE-4393.patch, MAPREDUCE-4393.patch, MAPREDUCE4393.patch, 
> MAPREDUCE4393.patch
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> This application is to demonstrate that YARN can be used for non-mapreduce 
> applications. As Hadoop has already been adopted and deployed widely and its 
> deployment in future will be highly increased, we thought that it's a good 
> potential to be used as PaaS.  
> I have implemented a proof of concept to demonstrate that YARN can be used as 
> a PaaS (Platform as a Service). I have done a gap analysis against VMware's 
> Cloud Foundry and tried to achieve as many PaaS functionalities as possible 
> on YARN.
> I'd like to check in this POC as a YARN example application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to