[
https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525434#comment-13525434
]
Suresh Srinivas commented on HDFS-4236:
---------------------------------------
bq. I think that is a bigger issue than the length limitation.
Agreed. But the incompatibility introduced in the change is unnecessary and is
also an important issue.
My comment is not just to track documenting incompatible change. We should add
a reasonable limit to the username length. As I said, this jira is essentially
tracking a comment against HDFS-4171 change and it needs to be addressed.
> 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
> Priority: Blocker
> 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
