You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:30:01 UTC

[jira] [Updated] (HADOOP-11518) Prefix-based per-RPC server configuration

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

Allen Wittenauer updated HADOOP-11518:
--------------------------------------
    Labels: BB2015-05-TBR  (was: )

> 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
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-11518.patch, HADOOP-11518.v2.patch, HADOOP-11518.v3.patch, HADOOP-11518.v4.patch, HADOOP-11518.v5.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)