Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual connection #1

Open
krzysztofantczak opened this issue Apr 12, 2014 · 0 comments
Open

Manual connection #1

krzysztofantczak opened this issue Apr 12, 2014 · 0 comments

Comments

@krzysztofantczak
Copy link

Hi,

I'm playing around with node-1 and 'happening' modules with my little stack of distributed services. I'm already using multicast discovery there, but replacing it with node-1/happening seems to be very valid idea in my use case. Anyway, one part of my services exists behind firewall where multicast communication is blocked (external and identical network), my current implementation falls back to SRV lookup against my DNS to pick up closest hub IP and PORT to join 'manually' to the node-1 cluster. I'm not expecting to implement anything like that here, but it would be awesome to be able to join into cluster from outside of node-1 api (related to multicast), so i could use IP:PORT from DNS to connect my nodes.

I've tried to hack into _handleNodeUp method with valid banner object and target host+port, this._sub.connect doesn't throw any errors but yet events are not emitted/received between 2 clusters.

One more thing. i think i should play with it a little bit more, but there is no way ( i didn't found one yet ) to gracefully catch mdns2 exception about missing dns service - which is thrown when You drop udp packets on your firewall - also here, no way to deal with simple situation by switching into alternative discovery method.

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

No branches or pull requests

1 participant