non-exclusive dgram bind can cause cluster exceptions
focusaurus opened this issue · 1 comments
focusaurus commented
So some versions of node have this bug: nodejs/node-v0.x-archive#9261
It is triggered when a clustered node process uses client datagram sockets.
There's a workaround to bind your client sockets with {exclusive: true}
to opt them out of cluster sharing (details in the bug report).
Wonder if you'd consider adding the workaround to this library. I'm seeing it manifest in the node-dogstatsd fork of this module, but can't file issues on the fork, so I'm hoping to get it patched upstream then get the node-dogstatsd maintainer to pull the fix downstream.
focusaurus commented
CC @joybro ^^