[
https://issues.apache.org/jira/browse/HDFS-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507758#comment-13507758
]
Suresh Srinivas commented on HDFS-4236:
---------------------------------------
bq. Yes, makes sense. Or we could add a config option to disable the 31 check,
thus enabling longer than 31 chars for OSes where this is supported, and the
default would be 31 check enabled.
Adding config option in this case seems unnecessary to me. Lets have reasonable
and larger username length.
BTW can you please mark both HDFS-4171 and this jira as incompatible, add
release notes to indicate the same with details and move these jiras to
incompatible section in CHANGES.txt?
> 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
