[
https://issues.apache.org/jira/browse/YARN-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908751#comment-13908751
]
Vinod Kumar Vavilapalli commented on YARN-1695:
-----------------------------------------------
I missed your comment, apologies.
We already have a clear security story for web UI and web-services. This JIRA
is not adding any more end-points than what are already present.
Similarly, we already expose the same information via RPCs, web UI _and_
web-services. So this JIRA isn't adding any more maintenance burden than is
already present.
Overall, I've seen a lot of use-cases where, at-least on the client side APIs,
users want to use web-services directly instead of writing code. That's the
goal of this JIRA. As I already pointed out, the remaining protocols from this
JIRA are in the grey area of whether to do or not at all and which I am not
focusing on at all right-away.
> 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)
