[
https://issues.apache.org/jira/browse/YARN-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814690#comment-13814690
]
Mayank Bansal commented on YARN-1266:
-------------------------------------
Thanks [~vinodkv] and [~zjshen] for the review.
bq. This is not enough, you need a client wrapper too.
Yes you are correct and thats part of YARN-967 as all the clients side (CLI)
changes are part of this JIRA.
bq. If so, I think it makes sense, and probably simplifies the problem.
However, I still have one concern about the independency of AHS. Let's say if
we want AHS to be a separate process like JHS in the future (or maybe now, see
my comments in YARN-955), when RM is stopped, AHS can not be accessed via RPC
interface.
I think AHS should be a seprate process thats how it can scale. What I think is
we still should have two seprate protocols to have the seprate RPC entry for RM
and AHS however we should be having same methods in both the protocol. May be
in client protocol and then history protocol can derive from that.
> Adding ApplicationHistoryProtocolPBService
> ------------------------------------------
>
> Key: YARN-1266
> URL: https://issues.apache.org/jira/browse/YARN-1266
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Mayank Bansal
> Assignee: Mayank Bansal
> Attachments: YARN-1266-1.patch, YARN-1266-2.patch
>
>
> Adding ApplicationHistoryProtocolPBService to make web apps to work and
> changing yarn to run AHS as a seprate process
--
This message was sent by Atlassian JIRA
(v6.1#6144)
