[jboss-jira] [JBoss JIRA] (JGRP-1568) Probe: make usable with TCP based configuration
Bela Ban (JIRA)
jira-events at lists.jboss.org
Tue May 28 04:59:06 EDT 2013
[ https://issues.jboss.org/browse/JGRP-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777294#comment-12777294 ]
Bela Ban commented on JGRP-1568:
--------------------------------
We can get a response from a DiagnosticsHandler by sending a datagram packet to hostname:7500, e.g. probe.sh -addr 192.168.1.5 -port 7500.
However, this will only return information about that specific instance.
We could get information from all nodes as follows:
* Check if the addr is a class D address. If so -> normal behavior
* Else send a first probe to hostname:7500 returning the desired info, *but also a list of physical addresses of the other instances*, e.g.
192.168.1.5:7500,192.168.1.1:7500,192.168.1.7:7500
* After this, we can send a probe to each of those instances as UDP datagram packet
> Probe: make usable with TCP based configuration
> -----------------------------------------------
>
> Key: JGRP-1568
> URL: https://issues.jboss.org/browse/JGRP-1568
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.4
>
>
> Probe currently requires IP multicasting. The goal is to also be able to use probe.sh with TCP based configs.
> SOLUTION:
> - Specify one or more IP address:port pairs when starting probe.sh
> - probe.sh will connect to all provided addresses in turn until one responds
> - The response contains the requested information and the full list of all member addresses
> - probe.sh then contacts all members (excluding the ones from which it already received information)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list