Type: New Feature
Affects Version/s: None
Fix Version/s: None
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.
|Provide RESTful equivalent of YarnClientImpl||Open||Unassigned|