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