Replaced ping-based healthcheck with net.createConnection#351
Open
mutantcornholio wants to merge 1 commit into3rd-Eden:masterfrom
Open
Replaced ping-based healthcheck with net.createConnection#351mutantcornholio wants to merge 1 commit into3rd-Eden:masterfrom
mutantcornholio wants to merge 1 commit into3rd-Eden:masterfrom
Conversation
Older ping-based healthcheck had a bunch of problems: * Doesn't work in ipv6-only environment (because of calling `ping`, not `ping6`) * Doesn't work if ICMP is blocked, but TCP is not * Doesn't work as expected if TCP on this exact port is firewalled out * Uses a lot of CPU on process spawning, may cause DoS in clusters with large number of worker processes Healthcheck with net.createConnection seems to be a much simpler and more robust alternative Two test were needed changing: * One was implicitly tied to ping interval; ECONNREFUSED was thrown faster, I've tuned reconnect timeout in test * Another one actually relied upon one of aforementioned problems: setting up server at 127.0.0.1:1234 would mean server is available to ping, but not to TCP connection. In that test, I've used net.listen to actually listen for connections on socket
Author
|
Test are faililng on nodejs 4/5 because mocha@^4 uses object destructuring, which isn't supported by those versions of node. Downgrading to mocha@^3 helps |
Author
|
@3rd-Eden what do you think? |
Author
|
@mapleeit, @kevin-greene-ck, looks like you are maintainers now? |
Author
|
Anyone? @3rd-Eden @mapleeit @kevin-greene-ck ? |
|
@mutantcornholio @3rd-Eden Any one working to integrate this, we are in environment without ping command, this will help us. |
Author
|
I've published fork here: This PR is the only difference in code now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Older ping-based healthcheck had a bunch of problems:
ping, notping6).large number of worker processes.
Healthcheck with net.createConnection seems to be a much simpler and
more robust alternative
Two test were needed changing:
I've tuned reconnect timeout in test
setting up server at 127.0.0.1:1234 would mean server is available to
ping, but not to TCP connection. In that test, I've used
net.listen to actually listen for connections on socket