-
Notifications
You must be signed in to change notification settings - Fork 166
Process never exits after statsd use #71
Comments
statsd.increment('my_counter', null, null, null, function() {
statsd.close();
}); |
I'm just new to this library today, and maybe I'm doing something wrong, but adding a call to Here's my (Typescript) code:
With the last line commented out, I see the increment message on my Statsd server, but the process doesn't end, as the OP found. When I uncomment the This is on OSX, Node 8.6.0, and node-statsd 0.1.1. |
@rgitzel Move the call to |
Hi everyone, if using this lib in aws lambda, the event loop never becomes empty and it doesn't exist until time out. Would it be possible to capture this requirement somewhere in the docs? I would be happy to do so if someone would advise on my pr? Thanks |
The code
prints "Done" then exits.
However, once I introduce a statsd client, the process never exists.
The output is
Is there a way to tell statsd that it should cleanup and not keep the node process alive?
The text was updated successfully, but these errors were encountered: