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

Vrushali C commented on HADOOP-10550:
-------------------------------------

It looks like this is not an issue anymore on trunk? 
Latest HttpAuthentication.md on trunk has the wording as "ResourceManager, 
NameNode, NodeManagers and DataNodes)" 

https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-
common/src/site/markdown/HttpAuthentication.md

Also, in hadoop-common, I see the following, so I think there isn't anything to 
fix here? 

{code}
[machine-channapattan hadoop-common-project (trunk)]$ grep -rni jobtracker * | 
grep md | grep -vi changes  | grep -vi releasenotes | grep -vi deprecatedproper
hadoop-common/src/main/bin/hadoop.cmd:58:@rem   HADOOP_{COMMAND}_OPTS etc  
HADOOP_JT_OPTS applies to JobTracker
hadoop-common/src/main/bin/hadoop.cmd:122:  set mapredcommands=pipes job queue 
mrgroups mradmin jobtracker tasktracker
hadoop-common/src/site/markdown/RackAwareness.md:114:#       |jobtracker|    
|datanode|
[machine-channapattan hadoop-common-project (trunk)]$
{code}


> HttpAuthentication.html is out of date
> --------------------------------------
>
>                 Key: HADOOP-10550
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10550
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.4.0, 3.0.0-alpha1
>            Reporter: Zhijie Shen
>            Assignee: Vrushali C
>            Priority: Minor
>              Labels: newbie, site
>
> It is still saying:
> {code}
> By default Hadoop HTTP web-consoles (JobTracker, NameNode, TaskTrackers and 
> DataNodes) allow access without any form of authentication.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to