[ https://issues.apache.org/jira/browse/YARN-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814639#comment-13814639 ]
Zhijie Shen commented on YARN-1266: ----------------------------------- bq. This is not enough, you need a client wrapper too. I think [~mayank_bansal] has it in another Jira. It seems that the work of ApplicationHistoryProtocol has been split into the following Jiras: YARN-979, YARN-1266, YARN-955 and YARN-967, and the client wrapper is in YARN-967. [~mayank_bansal], please correct me if I'm wrong. bq. I think we should just bite the bullet and remove ApplicationHistoryProtocol completely. We can merge the new APIs into ApplicationClientProtocol and take care of ResourceManager implementation of those APIs in a separate JIRA. Do you mean that we have a single RPC interface, and server-side implementation will redirect the query of completed applications/attempts/containers to AHS, right? 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. > 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)