hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13595) Rework hadoop_usage to be broken up by clients/daemons/etc.
Date Fri, 28 Apr 2017 23:15:04 GMT

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

Anu Engineer commented on HADOOP-13595:

bq. A non-privileged user can run diskbalancer and mover? That's... surprising. Also, mover
has the 

Sorry, I was not very clear. For diskbalancer you can read the data layout from the datanode
and create plan, you don't have to be an admin for that. But to submit that plan for execution
to the datanode, you need to be an admin. 

> Rework hadoop_usage to be broken up by clients/daemons/etc.
> -----------------------------------------------------------
>                 Key: HADOOP-13595
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13595
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HADOOP-13595.00.patch, HADOOP-13595.01.patch
> Part of the feedback from HADOOP-13341 was that it wasn't obvious what was a client and
what was a daemon.  Reworking the hadoop_usage output so that it is obvious helps fix this

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message