[
https://issues.apache.org/jira/browse/HADOOP-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138454#comment-14138454
]
Hadoop QA commented on HADOOP-10982:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669617/HADOOP-10982.patch
against trunk revision 47e5e19.
{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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms:
org.apache.hadoop.crypto.key.kms.server.TestKMS
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4753//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4753//console
This message is automatically generated.
> KMS: Support for multiple Kerberos principals
> ---------------------------------------------
>
> Key: HADOOP-10982
> URL: https://issues.apache.org/jira/browse/HADOOP-10982
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Andrew Wang
> Assignee: Alejandro Abdelnur
> Attachments: HADOOP-10982.patch, HADOOP-10982.patch,
> HADOOP-10982.patch
>
>
> The Key Management Server should support multiple Kerberos principals.
> This is required for KMS multi instance setups behind a VIP. In such
> scenarios there must a principal with the VIP hostname and one with the
> actual hostname of the KMS instance. Regular users will use the VIP entry
> point, monitoring agents must hit a specific instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
