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
Right now libcluster doesn't seem to be able to send messages across cluster. From what I can tell after looking at :publish implementation, the event is only sent to subscribers, which are processes on that same node, but not nodes in cluster (correct me if I'm wrong).
I am using epmd strategy. The way I'm testing it is this:
I've removed Cluster.Events from libcluster as part of the 2.0 effort to bring libcluster into alignment with firenest. libcluster is really intended to only provide the means by which you cluster nodes, beyond that though, things like firenest will be where you go for distributed pub/sub. Currently, swarm can work as a distributed pub/sub library, but firenest is going to be a better solution for that when it is released.
Right now
libcluster
doesn't seem to be able to send messages across cluster. From what I can tell after looking at:publish
implementation, the event is only sent to subscribers, which are processes on that same node, but not nodes in cluster (correct me if I'm wrong).I am using
epmd
strategy. The way I'm testing it is this:Run nodes:
Connect nodes:
Subscribe both shells to cluster events:
Publish event from within
node1
:Flush shell messages on both nodes:
on node1:
and on node2:
Was this done by design? If so, what is the purpose of publishing events within the same node?
At the same time
nodeup
andnodedown
events work perfectly across the cluster.Is there a plan to support publishing arbitrary events across cluster? If so, I'd like to work on a PR to bring this support.
The text was updated successfully, but these errors were encountered: