You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org> on 2012/02/15 20:47:00 UTC
[jira] [Commented] (MAPREDUCE-3864) Fix cluster setup docs for
correct SNN HTTPS parameters
[ https://issues.apache.org/jira/browse/MAPREDUCE-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208725#comment-13208725 ]
Hadoop QA commented on MAPREDUCE-3864:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12514673/mr-3864.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+0 tests included. The patch appears to be a documentation patch that doesn't require tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1864//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1864//console
This message is automatically generated.
> Fix cluster setup docs for correct SNN HTTPS parameters
> -------------------------------------------------------
>
> Key: MAPREDUCE-3864
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3864
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: documentation, security
> Affects Versions: 0.23.1
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: mr-3864.txt
>
>
> Currently the docs reference dfs.namenode.secondary.https-address, which does not exist. Instead it should reference dfs.namenode.secondary.https-port (new name of dfs.secondary.https.port as of HDFS-2950)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira