[jboss-jira] [JBoss JIRA] Updated: (JGRP-135) Common discovery multicast address/port
[ http://jira.jboss.com/jira/browse/JGRP-135?page=all ]
Jimmy Wilson updated JGRP-135:
------------------------------
Description:
In TP, we create a listener on 224.0.0.75:7500 (hard-coded, fixed multicast address/port).
When pinged, it returns information in key/value format, such as
- clusterName: DefaultPartition
- address: 192.168.5.1
- version: 2.2.9
- members: 192.168.5.1, 192.168.34.2, 192.168.0.2
- configuration: "UDP:FD:GMS"
The format is simple: keys and values are both strings, so we can have programmatic
discovery of clusters.
If the returned information is > 1472 bytes (ethernet MTU - IP and UDP datagram size),
then we simply break up the reply into multiple packets, each packet has to have the
clusterName and address fields present though, to identify them.
This might be used in the future to not just query information, but also submit commands.
To ensure future compatibility, make sure to design the format in an extensible way, e.g.
keys and values are strings.
was:
In TP, we create a listener on 224.0.0.5:7500 (hard-coded, fixed multicast address/port).
When pinged, it returns information in key/value format, such as
- clusterName: DefaultPartition
- address: 192.168.5.1
- version: 2.2.9
- members: 192.168.5.1, 192.168.34.2, 192.168.0.2
- configuration: "UDP:FD:GMS"
The format is simple: keys and values are both strings, so we can have programmatic
discovery of clusters.
If the returned information is > 1472 bytes (ethernet MTU - IP and UDP datagram size),
then we simply break up the reply into multiple packets, each packet has to have the
clusterName and address fields present though, to identify them.
This might be used in the future to not just query information, but also submit commands.
To ensure future compatibility, make sure to design the format in an extensible way, e.g.
keys and values are strings.
Fixed typo.
Common discovery multicast address/port
---------------------------------------
Key: JGRP-135
URL: http://jira.jboss.com/jira/browse/JGRP-135
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.2.9
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.2.9
In TP, we create a listener on 224.0.0.75:7500 (hard-coded, fixed multicast
address/port). When pinged, it returns information in key/value format, such as
- clusterName: DefaultPartition
- address: 192.168.5.1
- version: 2.2.9
- members: 192.168.5.1, 192.168.34.2, 192.168.0.2
- configuration: "UDP:FD:GMS"
The format is simple: keys and values are both strings, so we can have programmatic
discovery of clusters.
If the returned information is > 1472 bytes (ethernet MTU - IP and UDP datagram size),
then we simply break up the reply into multiple packets, each packet has to have the
clusterName and address fields present though, to identify them.
This might be used in the future to not just query information, but also submit commands.
To ensure future compatibility, make sure to design the format in an extensible way, e.g.
keys and values are strings.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira