hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4236) Regression: HDFS-4171 puts artificial limit on username length
Date Sun, 02 Dec 2012 21:57:58 GMT

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

Suresh Srinivas commented on HDFS-4236:

I marked this jira as a blocker for 2.0.3, to ensure it gets picked up for the release.
> Regression: HDFS-4171 puts artificial limit on username length
> --------------------------------------------------------------
>                 Key: HDFS-4236
>                 URL: https://issues.apache.org/jira/browse/HDFS-4236
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.3-alpha
>            Reporter: Allen Wittenauer
>              Labels: regression
> HDFS-4171 made the invalid assumption that there is a common limit on user names at the
UNIX level.  Almost all modern systems, when running under a 64-bit kernel, use a pointer
instead of a char array in the passwd struct.  This makes usernames essentially unlimited.
> Additionally, IIRC, the only places where HDFS and the OS interact where the username
is touched is during group lookup.
> This limit is artificial and should be removed.  There is a very high risk that we will
break users, especially service accounts used for automated processes.

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