Skip to content

Closes #67. Change the way DataNode host names are specified to be more resilient to hostname resolution.#68

Merged
xkrogen merged 1 commit into
linkedin:masterfrom
xkrogen:ekrogen-build-fix
Oct 10, 2018
Merged

Closes #67. Change the way DataNode host names are specified to be more resilient to hostname resolution.#68
xkrogen merged 1 commit into
linkedin:masterfrom
xkrogen:ekrogen-build-fix

Conversation

@xkrogen

@xkrogen xkrogen commented Oct 8, 2018

Copy link
Copy Markdown
Collaborator

No description provided.

@xkrogen

xkrogen commented Oct 8, 2018

Copy link
Copy Markdown
Collaborator Author

Can't reproduce this locally, so submitting a patch to get a Travis CI run...

@xkrogen xkrogen force-pushed the ekrogen-build-fix branch from 7fc646c to 77c9d06 Compare October 8, 2018 19:05
@xkrogen

xkrogen commented Oct 8, 2018

Copy link
Copy Markdown
Collaborator Author

Travis CI passes again, and I tested this on our internal cluster as well. It looks like it fixes the issue.

I'm not totally sure what happened, but I suspect something changed in the Travis CI infrastructure such that the host name resolved differently, in a way that made the previous version no longer work properly.

@xkrogen xkrogen changed the title Closes #67. Attempt to fix the build by changing the way the host name is specified. Closes #67. Change the way DataNode host names are specified to be more resilient to hostname resolution. Oct 8, 2018
@xkrogen xkrogen merged commit 8c617c2 into linkedin:master Oct 10, 2018
@xkrogen xkrogen deleted the ekrogen-build-fix branch October 10, 2018 15:32
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.

2 participants