It seems that the static members are only known to the local Node and they are not broadcasted to other Nodes. I'll debug a bit to see why.
From: Raymond Feng Sent: Tuesday, October 13, 2009 10:43 AM To: [email protected] ; [email protected] Subject: Re: Tribes endpoint registry and multiple nodes At this point, we only broadcast the endpoints from the Node that owns it. That should explain the behavior you are seeing. For example, Node B owns EP2, and it receives EP1 from Node A and EP3 from Node C. Even Node C receives EP4, it doesn't replicate to Node B as Node C doesn't own EP4. This scheme was by intention to avoid duplicate messages for the same endpoint. Maybe we can have the Node broadcasts the endpoints it doesn't own to the static members. Thanks, Raymond From: ant elder Sent: Tuesday, October 13, 2009 10:15 AM To: [email protected] Subject: Re: Tribes endpoint registry and multiple nodes On Tue, Oct 13, 2009 at 8:11 AM, ant elder <[email protected]> wrote: Thanks Raymond thats fixed it for me, and in r824617 i've fixed the remote sca binding to use the correct host name so now distributed domains over multiple hosts really do seem to work. woohoo. ...ant Spoke too soon , it doesn't seem to work perfectly yet. Still trying to pin down exactly what and get a testcase but i think this is what happens - if there are say four nodes each with an endpoint and two of those are connected via a static route and each of those connects to another node with multicast then ideally all nodes would end up with all endpoints - NodeA -multicast- NodeB -staticRoute- NodeC -multicast- NodeD EP1 EP2 EP3 EP4 all nodes should get all endpoints but they only get: NodeA gets EP2 NodeB gets EP1 and EP3 NodeC gets EP2 and EP4 NodeD gets EP3 ...ant
