Skip to content
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.

non-exclusive dgram bind can cause cluster exceptions #56

Open
focusaurus opened this issue Jul 9, 2015 · 1 comment
Open

non-exclusive dgram bind can cause cluster exceptions #56

focusaurus opened this issue Jul 9, 2015 · 1 comment

Comments

@focusaurus
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant