[ 
https://issues.apache.org/jira/browse/YARN-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026824#comment-16026824
 ] 

Allen Wittenauer commented on YARN-6655:
----------------------------------------

bq. label (node delimited by a dot in the hostname) is limited to 63 characters

I'm not sure if this is correct.  It's very possible to have:

@ example.com
foo.bar   IN A 0.0.0.0

in DNS.  foo.bar would the label for a node in example.com.  In particular, RFC 
1143 says:

"Host software MUST handle host names of up to 63 characters and SHOULD handle 
host names of up to 255 characters."

If a site isn't using DNS (e.g., /etc/hosts, NIS+, or some other naming 
service), enforcing DNS restrictions comes across as somewhat arbitrary given 
RFC 1143.  

So I'm inclined to think that this should be a configurable limit, up to 255 
chars.

>  We should validate yarn native services application submission side to 
> ensure that the hostname should be less than 63 characters
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-6655
>                 URL: https://issues.apache.org/jira/browse/YARN-6655
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn-native-services
>    Affects Versions: yarn-native-services
>            Reporter: Karam Singh
>            Assignee: Billie Rinaldi
>             Fix For: yarn-native-services
>
>         Attachments: YARN-6655-yarn-native-services.001.patch
>
>
> According to RFC 1035 the length of a FQDN is limited to 255 characters, and 
> each label (node delimited by a dot in the hostname) is limited to 63 
> characters
> So  We should validate yarn native services application submission side to 
> ensure that the hostname should be less than 63 characters



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to