hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3907) Allow multiple users for local block readers
Date Mon, 10 Sep 2012 18:38:08 GMT

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

Aaron T. Myers commented on HDFS-3907:

bq. could we also get a test that tests the single-user case?

Couldn't hurt, but doing so would really only be testing the comma-separated-list configuration
parsing code, since the two-user case is pretty much just testing the single-user case twice.

bq. we should continue to test with a not allowed user and add a new test to test with the
other allowed user.

The current patch does this, it's just a little misleading since Eli changed the comment above
the disallowed user case which made it look like he removed it. In fact that case is still
tested down below.
> Allow multiple users for local block readers
> --------------------------------------------
>                 Key: HDFS-3907
>                 URL: https://issues.apache.org/jira/browse/HDFS-3907
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>    Affects Versions: 1.0.0, 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-3907.txt
> The {{dfs.block.local-path-access.user}} config added in HDFS-2246 only supports a single
user, however as long as blocks are group readable by more than one user the feature could
be used by multiple users, to support this we just need to allow both to be configured. In
practice this allows us to also support HBase where the client (RS) runs as the hbase system
user and the DN runs as hdfs system user. I think this should work secure as well since we're
not using impersonation in the HBase case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message