Use IP address instead of hostname to avoid a bug in libc #480
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On certain linux systems there seems to be a bug in libc which causes deadlock of Ruby interpreter.
It only happens when ruby tries to resolve a hostname and its specifically triggered with many short-lived Ruby processes e.g. Resque.
See issue - #466 - where the solution was to use IP address instead of hostname.
Also this comment that contains GDB trace of all threads seems to directly point to libc call to resolve hostname.