-
Bug
-
Resolution: Done
-
Critical
-
7.0.0.GA
In chapter 4.4.3. Data Replication we should stress that only one backup per live is supported (this holds also for Shared Store).
For EAP 7 we do not support dynamic way of pairing live with backup. Following paragraph should be removed:
Connect to any live server. This will be the behavior if group-name is not configured allowing a backup server to connect to any live server The backup will search for any live server that it is configured to connect to. It then tries to replicate with each live server in turn until it finds a live server that has no current backup configured. If no live server is available it will wait until the cluster topology changes, e.g. a node joins or leaves the cluster, and repeats the process.
In the paragraph where live/backup pairing is configured using node group, we should provide example where each live backup pair has unique name, for example:
Connect to a live server in the same node group. You can specify a group of live servers that a backup server can connect to. This is done by configuring a group-name in either the master or the slave element. A backup server will only connect to a live server that shares the same group-name
As an example of using a group-name, suppose you have 4 live servers and 4 backup servers. You could divide the servers into the following groups:
live1 and backup1 will have a group-name of pair1.
live2 and backup2 will have a group-name of pair2.
live3 and backup3 will have a group-name of pair3.
live4 and backup4 will have a group-name of pair4.
After joining the cluster the backup1 with a group-name of pair1 will search for live1 server with the same name.
