hadoop-common-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] (HADOOP-7214) Hadoop /usr/bin/groups equivalent
Date Tue, 05 Apr 2011 19:47:05 GMT

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

Aaron T. Myers commented on HADOOP-7214:

Hey Allen, what conclusion do you draw from this reasoning? That we shouldn't concern ourselves
with implementing a way to query the NN and JT independently, since having distinct group
resolutions on each is a misconfiguration? Or that we shouldn't provide a way to query either
the NN or JT for a user's groups since they should happen to be the same on the client?

I *might* agree with the first conclusion, but can't possible agree with the second. It's
perfectly reasonable to have clients which have different sets of users/groups from what's
on the servers. For example, at a one organization where I've worked, developers had self-managed
laptops, but were permitted to access Hadoop clusters as clients from these laptops. The laptops
obviously had different sets of users/groups than what was on these clusters.

> Hadoop /usr/bin/groups equivalent
> ---------------------------------
>                 Key: HADOOP-7214
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7214
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.23.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
> Since user -> groups resolution is done on the NN and JT machines, there should be
a way for users to determine what groups they're a member of from the NN's and JT's perspective.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message