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

Billie Rinaldi commented on YARN-8675:
--------------------------------------

Hey [~Jim_Brennan], thanks for taking a look. You're right, that javadoc should 
be updated. Regarding the case where net=host and the hostname is set by the 
AM, this works successfully for the service AM because it creates registry 
entries for this hostname. This is why I suggested changing the net=host 
behavior only for AMs that do not set the hostname. The issues we have 
encountered in this ticket and YARN-8027 regarding net=host have been about the 
default hostname based on the contaner ID that is created in the docker runtime 
when the AM has not provided a hostname. The issues should be resolved by not 
setting the default hostname when net=host, as in patch 2.

> Setting hostname of docker container breaks with "host" networking mode for 
> Apps which do not run as a YARN service
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-8675
>                 URL: https://issues.apache.org/jira/browse/YARN-8675
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Yesha Vora
>            Assignee: Suma Shivaprasad
>            Priority: Major
>              Labels: Docker
>         Attachments: YARN-8675.1.patch, YARN-8675.2.patch
>
>
> Applications like the Spark AM currently do not run as a YARN service and 
> setting hostname breaks driver/executor communication if docker version 
> >=1.13.1 , especially with wire-encryption turned on.
> YARN-8027 sets the hostname if YARN DNS is enabled. But the cluster could 
> have a mix of YARN service/native Applications.
> The proposal is to not set the hostname when "host" networking mode is 
> enabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to