[jboss-jira] [JBoss JIRA] (JGRP-1521) RELAY2: only some members can become site masters
[
https://issues.jboss.org/browse/JGRP-1521?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1521:
--------------------------------
RELAY2 has 2 new properties:
- enable_address_tagging (boolean): if false, we'll not generate special addresses
that embed the knowledge whether a member can become site master
- can_become_site_master (boolean): if false, this member can be skipped when determining
the next site master from a view
If we have a view that has all members marked with can_become_site_master=false, then we
pick the first member of the view. If we have a view {B,C} where both members don't
become site masters (but B is site master), when A joins (can_become_site_master=true),
then B will stop being the site master and A will take over.
RELAY2: only some members can become site masters
-------------------------------------------------
Key: JGRP-1521
URL: https://issues.jboss.org/browse/JGRP-1521
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.2
Currently, every node in a local cluster (site) can become site master (relaying messages
between sites). This requires an internal and external NIC; the former to talk to the
local cluster nodes, and the latter to talk to the remote sites.
If only a few nodes have multiple NIC, and/or access to the external world, then we
should be able to restrict who can become a site master and who cannot.
E.g. if we have view {A,B,C,D,E,F}, then perhaps only A and C can become site masters. In
this case, if A crashes or leaves, then *C* should become the new site master.
Investigate how feasible it is to implement selective site masters.
--
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