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 78A8B10FD3 for ; Thu, 26 Dec 2013 20:59:50 +0000 (UTC) Received: (qmail 20275 invoked by uid 500); 26 Dec 2013 20:59:50 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 20249 invoked by uid 500); 26 Dec 2013 20:59:50 -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 20240 invoked by uid 99); 26 Dec 2013 20:59:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Dec 2013 20:59:50 +0000 Date: Thu, 26 Dec 2013 20:59:50 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1523) Replace RMNotYetReadyException with the standard hadoop io StandbyException 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-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857071#comment-13857071 ] Karthik Kambatla commented on YARN-1523: ---------------------------------------- bq. Should we make the throwStandbyException() a method of HAUtil so that we could reuse it in other places if need be? Like the idea. Let us do it when we have another place that throws StandbyException. bq. When we want the standby RM to re-direct the client to the active RM then how do you think we would do that? The two options appear to be (1) notifying the client (through a derivate of StandbyException) that we are not Active and that the Active is so-and-so (2) relaying the client request to the Active RM and responding to the Client. The first approach might be simpler and have fewer round-trips overall, particularly if there are only few kinds of clients. Will commit this later today. > Replace RMNotYetReadyException with the standard hadoop io StandbyException > --------------------------------------------------------------------------- > > Key: YARN-1523 > URL: https://issues.apache.org/jira/browse/YARN-1523 > Project: Hadoop YARN > Issue Type: Sub-task > Affects Versions: 2.4.0 > Reporter: Bikas Saha > Assignee: Karthik Kambatla > Attachments: yarn-1523-1.patch > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)