You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: