[
https://issues.apache.org/jira/browse/HADOOP-14880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207607#comment-16207607
]
Hadoop QA commented on HADOOP-14880:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 2m
29s{color} | {color:red} Docker failed to build yetus/hadoop:0de40f0. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14880 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12892596/HADOOP-14880-2.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/13529/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> [KMS] Document&test missing KMS client side configs
> ---------------------------------------------------
>
> Key: HADOOP-14880
> URL: https://issues.apache.org/jira/browse/HADOOP-14880
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Wei-Chiu Chuang
> Assignee: Gabor Bota
> Priority: Minor
> Labels: newbie
> Attachments: HADOOP-14880-1.patch, HADOOP-14880-2.patch
>
>
> Similar to HADOOP-14783, I did a sweep of KMS client code and found an
> undocumented KMS client config. It should be added into core-site.xml.
> hadoop.security.kms.client.timeout
> From the code it appears this config affects both client side connection
> timeout and read timeout.
> In fact it doesn't looks like this config is tested. So would be really nice
> add a test for it as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
