[JBoss JIRA] (MODCLUSTER-303) Discovery protocol based on mod-cluster
by Martin Kamp Jensen (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-303?page=com.atlassian.jira.pl... ]
Martin Kamp Jensen edited comment on MODCLUSTER-303 at 4/15/15 8:14 AM:
------------------------------------------------------------------------
If I understand this correctly, this is exactly what we would benefit from. Note that we cannot use multicast.
Currently, we are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
- The first node (WildFly 8.2) is set up, mod_cluster and JGroups having proxy_list and initial_hosts, respectively, set up to point to the IP address of the node
- The first node is started
- Later, the second node is setup, mod_cluster and JGroups having proxy_list and initial_hosts, respectively, set up to point to the IP address of the new node in addition to the IP address of the first node
- The second node is started
- JGroups on boths nodes discovers both nodes
- mod_cluster on the first node discovers both nodes (maybe because mod_cluster of the second node, which has the IP address of the first node in its proxy_list, talks to the first node)
- mod_cluster on the second node only discovers itself
- A restart of the first node (with proxy_list updated to include both nodes) fixes the problem
was (Author: mkjensen):
If I understand this correctly, this is exactly what we would benefit from. Note that we cannot use multicast.
Currently, we are testing the following setup and experimenting a mod_cluster discovery issue/challenge:
- The first node (WildFly 8.2) is set up, mod_cluster and JGroups having proxy_list and initial_hosts, respectively, set up to point to the IP address of the node
- The first node is started
- Later, the second node is setup, mod_cluster and JGroups having proxy_list and initial_hosts, respectively, set up to point to the IP address of the new node in addition to the IP address of the first node
- The second node is started
- JGroups on boths nodes discovers both nodes
- mod_cluster on the first node discovers both nodes (maybe because mod_cluster of the second node, which has the IP address of the first node in its proxy_list, talks to the first node)
- mod_cluster on the second node only discovers itself
- A restart of the first node (with proxy_list updated to include both nodes) fixes the problem
> Discovery protocol based on mod-cluster
> ---------------------------------------
>
> Key: MODCLUSTER-303
> URL: https://issues.jboss.org/browse/MODCLUSTER-303
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Vladimir Blagojevic
> Assignee: Radoslav Husar
> Fix For: 1.3.1.Beta3
>
>
> In it previous life used to be https://issues.jboss.org/browse/JGRP-1322
> It would be nice to have a discovery protocol that can use mod-cluster as the source of the node information.
> Mod-cluster already knows the list of participating nodes and provides this information in a well known format, so it could be simple to implement.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
- 1
- 0
[JBoss JIRA] (MODCLUSTER-303) Discovery protocol based on mod-cluster
by Martin Kamp Jensen (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-303?page=com.atlassian.jira.pl... ]
Martin Kamp Jensen commented on MODCLUSTER-303:
-----------------------------------------------
If I understand this correctly, this is exactly what we would benefit from. Note that we cannot use multicast.
Currently, we are testing the following setup and experimenting a mod_cluster discovery issue/challenge:
- The first node (WildFly 8.2) is set up, mod_cluster and JGroups having proxy_list and initial_hosts, respectively, set up to point to the IP address of the node
- The first node is started
- Later, the second node is setup, mod_cluster and JGroups having proxy_list and initial_hosts, respectively, set up to point to the IP address of the new node in addition to the IP address of the first node
- The second node is started
- JGroups on boths nodes discovers both nodes
- mod_cluster on the first node discovers both nodes (maybe because mod_cluster of the second node, which has the IP address of the first node in its proxy_list, talks to the first node)
- mod_cluster on the second node only discovers itself
- A restart of the first node (with proxy_list updated to include both nodes) fixes the problem
> Discovery protocol based on mod-cluster
> ---------------------------------------
>
> Key: MODCLUSTER-303
> URL: https://issues.jboss.org/browse/MODCLUSTER-303
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Vladimir Blagojevic
> Assignee: Radoslav Husar
> Fix For: 1.3.1.Beta3
>
>
> In it previous life used to be https://issues.jboss.org/browse/JGRP-1322
> It would be nice to have a discovery protocol that can use mod-cluster as the source of the node information.
> Mod-cluster already knows the list of participating nodes and provides this information in a well known format, so it could be simple to implement.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
- 1
- 0