[YARN-1695] Implement the rest (writable APIs) of RM web-services

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Varun Vasudev
• Reporter: Vinod Kumar Vavilapalli
• Created: 07/Feb/14 18:21
• Updated: 10/Dec/14 15:01

Description

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.

Issue Links

• duplicates: YARN-1538 Support web-services for application-submission and AM protocols
• is depended upon by: SLIDER-170 switch to YARN Rest API for App creation
• is depended upon by: SLIDER-151 Implement full slider API in REST and switch client to it

Sub-Tasks

• Expose kill app functionality as part of RM web services: Closed
• Implement getnewapplication and submitapp as part of RM web service: Closed
• Implement web services to create, renew and cancel delegation tokens: Closed
• Allow RM web services users to authenticate using delegation tokens: Closed
• Provide RESTful equivalent of YarnClientImpl: Open