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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-11518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297290#comment-14297290 ] 

Hadoop QA commented on HADOOP-11518:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12695279/HADOOP-11518.patch
  against trunk revision 03a5e04.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5533//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5533//console

This message is automatically generated.

> 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
>
>
> 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)