Type: Feature Request
Status: Resolved (View Workflow)
Resolution: Duplicate Issue
Affects Version/s: 1.3.0.Final
Fix Version/s: None
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.