hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7214) Hadoop /usr/bin/groups equivalent
Date Sat, 02 Apr 2011 01:22:06 GMT

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

Allen Wittenauer commented on HADOOP-7214:

The root of the problem is an inconsistent namespace.  Trying to work around that is always
fraught with peril... which is why a lot of systems assume that it is flat/consistent across
all nodes in a given network.

But one thing comes to mind:  isn't this information already reported as part of the job conf?
 Shouldn't a user be able to query their job's information (at least via the web UI... probably
should have something shell-ish) to determine this information?  Granted, it would be nice
to know prior to job submission, but we're fundamentally looking at a debugging tool for broken

> 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