[
https://issues.apache.org/jira/browse/HDFS-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204306#comment-13204306
]
Todd Lipcon commented on HDFS-2917:
-----------------------------------
I think consistency with the other administrative operations (ie using
checkSuperUser as Eli has done in this patch) is preferable. Otherwise it's yet
another ACL that people have to configure rather than just "doing the right
thing".
{code}
+ } catch (IOException ioe) {
+ errOut.println("Operaton failed: " + ioe.getLocalizedMessage());
return -1;
{code}
if debug logs are enabled, can you log it including the stack trace?
Also, typo above ("Operaton")
> HA: haadmin should not work if run by regular user
> --------------------------------------------------
>
> Key: HDFS-2917
> URL: https://issues.apache.org/jira/browse/HDFS-2917
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Reporter: Aaron T. Myers
> Assignee: Eli Collins
> Fix For: HA branch (HDFS-1623)
>
> Attachments: hdfs-2917.txt
>
>
> Like dfsadmin, haadmin should require HDFS superuser privileges to work.
> Currently any user can use haadmin.
--
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
