hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1266) Adding ApplicationHistoryProtocolPBService
Date Wed, 06 Nov 2013 19:16:17 GMT

    [ https://issues.apache.org/jira/browse/YARN-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815171#comment-13815171
] 

Zhijie Shen commented on YARN-1266:
-----------------------------------

bq.  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.

Correct my previous comment. It seems that we can have a single protocol, but AHS can have
separate server-side implementation of it. YarnClient will then be modified to query the completed
applications/attempts/containers from the AHS's implementation instead. It's similar to MRClientProtocol,
which has two implementations in MR and in JHS.

 bq. May be in client protocol and then history protocol can derive from that.

In JHS, it is this case: HSClientProtocol derives MRClientProtocol without adding more methods.
Hence, the derivation seems to be unnecessary.

> 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)

Mime
View raw message