[teiid-issues] [JBoss JIRA] Commented: (TEIID-233) Server should support JGroups communication over P2P

[Ramesh Reddy (JIRA)]

    [ https://jira.jboss.org/jira/browse/TEIID-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465055#action_12465055 ] 

Ramesh Reddy commented on TEIID-233:
------------------------------------

To support the all the cluster combinations, the following properties will be added to the configuration (some of previous properties are renamed)

# cluster.use_multicast = true Multicast used, false Unicast used
# cluster.protocol = TCP or UDP (if unicast)
# cluster.unicast.members = comma separated list of cluster hosts if TCP Unicast in use. (Ex: config.name=host.name, config.name=host.name) 
# If UDP Unicast this refers to single gossip server (ex:host[port])
# cluster.multicast.address = blank address will default to 224.xx.xx.xx where xx is current host IP.
# cluster.port= Can be multicast port or TCP Unicast port	

cluster.use_multicast=false
cluster.protocol=TCP
cluster.unicast.members=
cluster.multicast.address=
cluster.port=5555
cluster.name=TEIID-CLUSTER

During the installation, the properties are used as following

"cluster.use_multicast = true", then multicast is used, then user need to specify

1. cluster.multicast.address=224.xx.xx.xx
2. cluster.port=5555
3. cluster.name=my-cluster-name

When the "cluster.use_multicast = false", the Unicast is in use, now use has choice of using TCP or UDP protocols

if (cluster.protocol=TCP ) then
        cluster.port=5555
        cluster.unicast.members=specifies all the cluster members
end
else if (cluster.protocol=UDP ) then
        cluster.unicast.members= specifies the gossip router information
end

When "TCP" based clustering is used (default mode)

The "cluster.unicast.members" property will be stored in the bootstrap properties. This property can be specified by the user during installation of server as to what are all the cluster members (with their host names), or user can edit this file at a later date manually when they add a new cluster member.  If this file is not edited then, discovery is not possible.

There are couple methods of discovery is possible, but they all come with certain disadvantages of maintenance of the runtime configuration information. More over that can be add-on to this process at a later date as the requirement arises. 


> Server should support JGroups communication over P2P
> ----------------------------------------------------
>
>                 Key: TEIID-233
>                 URL: https://jira.jboss.org/jira/browse/TEIID-233
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 6.0.0
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>             Fix For: 6.1.0
>
>
> Currently Server only supports the JGroups over Multicast we need to support unicast protocol tool, with configuration.

-- 
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