On Thu, Dec 10, 2009 at 5:33 PM, Raymond Feng <[email protected]> wrote: > Let's take an example, say A is configured to add B as the static member. > When the tribes-based endpoint registry is started on A, it adds B (hostB, > portB). When the registry is started on B, we don't customize the receiver > port and the default one is used. Based on 2, I think the TcpFailureDetector > tries to contact hostB/portB to decide if B should be added to membership so > that other nodes can see it. If portB != B's receiver port, B is not added.
Right, but i'm not sure I understand the point you're trying to make? Are you saying that as the default port is the same at both ends then its ok for A to use the value of As default port as its static route port value as thats going to be the same as B will be using? If so then i dont think so because the default port is only the initial value and as more runtimes get started its goes up - 4000, 4001, 4002 etc - using the default might work as an easy default but you still need to be able to explicitly configure it. > > For the case that A connects to B and C, do we only set up a static route on > A? Yes that would be the ideal - so multicast will work for a bunch of nodes local to each other and then a subset of those nodes can have static routes to other remote nodes and those othere nodes may have their own local multicast group of nodes and any of those could also have other remote static route connections, and the result would be all nodes would see all endpoints. ...ant
