[ https://issues.apache.org/jira/browse/YARN-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908754#comment-13908754 ]
Vinod Kumar Vavilapalli commented on YARN-1695: ----------------------------------------------- There is a related question here - whether to implement web-services inside RM or pull them out and implement them in a proxy layer similar to WebHDFS. But that's a larger issue with code and feature-set that is already present today. Will create a separate ticket for that discussion. > Implement the rest (writable APIs) of RM web-services > ----------------------------------------------------- > > Key: YARN-1695 > URL: https://issues.apache.org/jira/browse/YARN-1695 > Project: Hadoop YARN > Issue Type: New Feature > Reporter: Vinod Kumar Vavilapalli > Assignee: Vinod Kumar Vavilapalli > > MAPREDUCE-2863 added the REST web-services to RM and NM. But all the APIs > added there were only focused on obtaining information from the cluster. We > need to have the following REST APIs to finish the feature > - Application submission/termination (Priority): This unblocks easy client > interaction with a YARN cluster > - Application Client protocol: For resource scheduling by apps written in an > arbitrary language. Will have to think about throughput concerns > - ContainerManagement Protocol: Again for arbitrary language apps. > One important thing to note here is that we already have client libraries on > all the three protocols that do some some heavy-lifting. One part of the > effort is to figure out if they can be made any thinner and/or how > web-services will implement the same functionality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)