[ https://jira.jboss.org/jira/browse/TEIID-233?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-233: ------------------------------------ There is discussion thread on this. The summary is of it is The user would have those three deployment options. Our default would be Unicast over TCP using an embedded router that supports fail-over. Option two would be Multicast over UDP (what we do now by default) and option three would be Unicast over UDP or TCP using GossipRouter. Further discussions as to implementations of Option 1, the following is being considered When a primary server process starts, it will start a gossip server. When a secondary host being added, the installation requires the user to specify the primary server, at the same this can be extended such that user has to specify the gossip port of the primary server, and this information is saved along with bootstrap properties file. The primary server's bootstrap properties either now needs to be updated manually or automatically about the second server, so that when either server goes down and comes back up, they know about each other to cluster back up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira