[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-455?page=com.atlassian.jira.pl... ]
Radoslav Husar commented on MODCLUSTER-455:
-------------------------------------------
You may have misunderstood the purpose of the mod_cluster project/subsystem. It registers nodes with the loadbalancer, for session clustering see the Infinispan/JGroups subsystems.
Feature request at MODCLUSTER-303 is about supporting JGroups discovery using mod_cluster loadbalancer.
> Discovery using proxy_list of newly added nodes
> -----------------------------------------------
>
> Key: MODCLUSTER-455
> URL: https://issues.jboss.org/browse/MODCLUSTER-455
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.0.Final
> Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
> Reporter: Martin Kamp Jensen
> Assignee: Radoslav Husar
> Attachments: first-modclustermanager.log, first-server.log, httpd-site, second-modclustermanager.log, second-server.log, wildflyconfig.xml
>
>
> I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
> We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
> - The first node 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 set up, 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
> In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-455?page=com.atlassian.jira.pl... ]
Radoslav Husar resolved MODCLUSTER-455.
---------------------------------------
Resolution: Duplicate Issue
> Discovery using proxy_list of newly added nodes
> -----------------------------------------------
>
> Key: MODCLUSTER-455
> URL: https://issues.jboss.org/browse/MODCLUSTER-455
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.0.Final
> Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
> Reporter: Martin Kamp Jensen
> Assignee: Radoslav Husar
> Attachments: first-modclustermanager.log, first-server.log, httpd-site, second-modclustermanager.log, second-server.log, wildflyconfig.xml
>
>
> I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
> We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
> - The first node 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 set up, 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
> In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-455?page=com.atlassian.jira.pl... ]
Radoslav Husar reopened MODCLUSTER-455:
---------------------------------------
> Discovery using proxy_list of newly added nodes
> -----------------------------------------------
>
> Key: MODCLUSTER-455
> URL: https://issues.jboss.org/browse/MODCLUSTER-455
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.0.Final
> Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
> Reporter: Martin Kamp Jensen
> Assignee: Radoslav Husar
> Attachments: first-modclustermanager.log, first-server.log, httpd-site, second-modclustermanager.log, second-server.log, wildflyconfig.xml
>
>
> I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
> We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
> - The first node 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 set up, 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
> In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-455?page=com.atlassian.jira.pl... ]
Radoslav Husar closed MODCLUSTER-455.
-------------------------------------
Assignee: Radoslav Husar (was: Jean-Frederic Clere)
Resolution: Done
> Discovery using proxy_list of newly added nodes
> -----------------------------------------------
>
> Key: MODCLUSTER-455
> URL: https://issues.jboss.org/browse/MODCLUSTER-455
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.0.Final
> Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
> Reporter: Martin Kamp Jensen
> Assignee: Radoslav Husar
> Attachments: first-modclustermanager.log, first-server.log, httpd-site, second-modclustermanager.log, second-server.log, wildflyconfig.xml
>
>
> I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
> We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
> - The first node 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 set up, 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
> In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 10 months
[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Martin Kamp Jensen (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-455?page=com.atlassian.jira.pl... ]
Martin Kamp Jensen updated MODCLUSTER-455:
------------------------------------------
Attachment: wildflyconfig.xml
httpd-site
Attached WildFly config and httpd site config.
> Discovery using proxy_list of newly added nodes
> -----------------------------------------------
>
> Key: MODCLUSTER-455
> URL: https://issues.jboss.org/browse/MODCLUSTER-455
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.0.Final
> Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
> Reporter: Martin Kamp Jensen
> Assignee: Jean-Frederic Clere
> Attachments: first-modclustermanager.log, first-server.log, httpd-site, second-modclustermanager.log, second-server.log, wildflyconfig.xml
>
>
> I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
> We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
> - The first node 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 set up, 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
> In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Martin Kamp Jensen (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-455?page=com.atlassian.jira.pl... ]
Martin Kamp Jensen updated MODCLUSTER-455:
------------------------------------------
Attachment: second-server.log
first-server.log
second-modclustermanager.log
first-modclustermanager.log
Attached WildFly server log and mod_cluster manager output from both nodes.
> Discovery using proxy_list of newly added nodes
> -----------------------------------------------
>
> Key: MODCLUSTER-455
> URL: https://issues.jboss.org/browse/MODCLUSTER-455
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.3.0.Final
> Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
> Reporter: Martin Kamp Jensen
> Assignee: Jean-Frederic Clere
> Attachments: first-modclustermanager.log, first-server.log, second-modclustermanager.log, second-server.log
>
>
> I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
> We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
> - The first node 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 set up, 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
> In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (MODCLUSTER-455) Discovery using proxy_list of newly added nodes
by Martin Kamp Jensen (JIRA)
Martin Kamp Jensen created MODCLUSTER-455:
---------------------------------------------
Summary: Discovery using proxy_list of newly added nodes
Key: MODCLUSTER-455
URL: https://issues.jboss.org/browse/MODCLUSTER-455
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.3.0.Final
Environment: RHEL 6.5, Java 8u25, WildFly 8.2, httpd 2.2.15
Reporter: Martin Kamp Jensen
Assignee: Jean-Frederic Clere
I'm not sure if the following is working as designed or if its a bug. Note that we cannot use multicast.
We are testing the following setup and experiencing a mod_cluster discovery issue/challenge:
- The first node 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 set up, 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
In conclusion, since we cannot use multicast, we have to restart because then _proxy_list_ of both nodes contains the IP addresses of both nodes. It would be helpful if mod_cluster would discover like JGroups, enabling us to add additional nodes without restarts.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (MODCLUSTER-303) Discovery protocol based on mod-cluster
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-303?page=com.atlassian.jira.pl... ]
Bela Ban commented on MODCLUSTER-303:
-------------------------------------
Yes, the idea behind this is that since workers (Wildfly instances) already register with all httpds, we might as well use this information for JGroups nodes to discover each other. This would be done by essentially asking the httpd instance(s) for discovery information: each JGroups/Wildfly node would register its information with httpd, and would thus be able to discover information about other nodes.
The advantage of this would be that we could piggy back discovery on an existing infrastructure.
Of course, this doesn't revent other discovery mechanisms from being used.
> 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)
9 years, 11 months
[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:22 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 set up, 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
Edit: After reading again, I should probably have commented on MODCLUSTER-282. Also, it seems I got it the wrong way round. You are probably working on getting JGroups to discover nodes via mod_cluster, not getting mod_cluster to see the same nodes as JGroups. Anyway, I'm still interested in a solution to the setup described above and I would be happy to put the question/request elsewhere.
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 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 set up, 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)
9 years, 11 months
[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:15 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 set up, 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 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
> 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)
9 years, 11 months