Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 6 Feb 2015 21:47:35 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12771027.1422541574000.284513.1423259255126@Atlassian.JIRA>
In-Reply-To: <JIRA.12771027.1422541574000@Atlassian.JIRA>
References: <JIRA.12771027.1422541574000@Atlassian.JIRA>
 <JIRA.12771027.1422541574605@arcas>
Subject: [jira] [Updated] (HADOOP-11518) Prefix-based per-RPC server
 configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-11518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee updated HADOOP-11518:
--------------------------------
    Status: Open  (was: Patch Available)

> Prefix-based per-RPC server configuration
> -----------------------------------------
>
>                 Key: HADOOP-11518
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11518
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>         Attachments: HADOOP-11518.patch, HADOOP-11518.v2.patch, HADOOP-11518.v3.patch
>
>
> If a process runs multiple RPC servers, there is no way to individually set their IPC parameters beyond what's supported by the RPC Builder.  If a configuration is shared among many nodes, this is more problematic. 
> In this jira, a prefix-based per-server configuration is proposed.  When an RPC server is built, a prefix can be specified, which will then be prepended to keys when retrieving configured values.  There will be an option to fall-back to using the key without the prefix when no value is found with the prefix, thus making this feature compatible with the current way of configuring servers.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)