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 1398519A94 for ; Tue, 12 Apr 2016 18:52:27 +0000 (UTC) Received: (qmail 36397 invoked by uid 500); 12 Apr 2016 18:52:26 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 36333 invoked by uid 500); 12 Apr 2016 18:52:25 -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 36292 invoked by uid 99); 12 Apr 2016 18:52:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2016 18:52:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AAD2D2C1F56 for ; Tue, 12 Apr 2016 18:52:25 +0000 (UTC) Date: Tue, 12 Apr 2016 18:52:25 +0000 (UTC) From: "Jonathan Maron (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-4952) need configuration mechanism for specifying per-host network interface MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jonathan Maron created YARN-4952: ------------------------------------ Summary: need configuration mechanism for specifying per-host network interface Key: YARN-4952 URL: https://issues.apache.org/jira/browse/YARN-4952 Project: Hadoop YARN Issue Type: Sub-task Reporter: Jonathan Maron Assignee: Jonathan Maron The initial configuration approach for the DNS service specified a bind-address that designated the network interface to which the service should bind its listener port. However, there is a need to potentially specify multiple DNS service instances (HA approach) and therefore a need to specify bind addresses for each instance (and those interfaces may vary between hosts). This may take a for similar to the RM HA approach (rm1, rm2) -- This message was sent by Atlassian JIRA (v6.3.4#6332)