Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BBC84104A1 for ; Wed, 6 Nov 2013 19:16:18 +0000 (UTC) Received: (qmail 46958 invoked by uid 500); 6 Nov 2013 19:16:17 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 46912 invoked by uid 500); 6 Nov 2013 19:16:17 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 46733 invoked by uid 99); 6 Nov 2013 19:16:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 19:16:17 +0000 Date: Wed, 6 Nov 2013 19:16:17 +0000 (UTC) From: "Zhijie Shen (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1266) Adding ApplicationHistoryProtocolPBService MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)