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

2014-07-15 Thread Vinod Kumar Vavilapalli (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kumar Vavilapalli updated YARN-1695:
--

Priority: Major  (was: Blocker)

> 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: Varun Vasudev
>
> 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.2#6252)


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

2014-06-27 Thread Karthik Kambatla (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karthik Kambatla updated YARN-1695:
---

Priority: Blocker  (was: Major)

> 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: Varun Vasudev
>Priority: Blocker
>
> 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.2#6252)