Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use NM_HOST to determine hostname #97

Merged
merged 1 commit into from Oct 29, 2018
Merged

Use NM_HOST to determine hostname #97

merged 1 commit into from Oct 29, 2018

Conversation

jcrist
Copy link
Owner

@jcrist jcrist commented Oct 29, 2018

Some clusters have infiniband enabled, which may get picked up by
InetAddress when determining the application-master hostname/IP.
Infiniband is not currently supported by gRPC, so this would result in
failures. Instead of trying to more robustly determine the IP for a
supported network interface, we rely on the NM_HOST environment
variable, which is always set and must resolve correctly on all nodes
for hadoop to properly work.

Some clusters have infiniband enabled, which may get picked up by
`InetAddress` when determining the application-master hostname/IP.
Infiniband is not currently supported by gRPC, so this would result in
failures. Instead of trying to more robustly determine the IP for a
supported network interface, we rely on the `NM_HOST` environment
variable, which is always set and must resolve correctly on all nodes
for hadoop to properly work.
@jcrist jcrist merged commit 9bd81d2 into master Oct 29, 2018
@jcrist jcrist deleted the use-nm-host branch October 29, 2018 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant