Setting Up Replication Using Ssl - Oracle 5.0 Reference Manual

Figure 16.5. Redundancy Using Replication, After Master Failure
When
Master
and
Slave 2
writes that it missed while it was down.
To make
Master
preceding procedure as if
this procedure, do not forget to run
and
Slave 3
point at which
Note that there is no synchronization between the different slaves to a master. Some slaves might
be ahead of others. This means that the concept outlined in the previous example might not work. In
practice, however, the relay logs of different slaves will most likely not be far behind the master, so it
would work, anyway (but there is no guarantee).
A good way to keep your applications informed as to the location of the master is by having a dynamic
DNS entry for the master. With

16.3.7. Setting Up Replication Using SSL

To use SSL for encrypting the transfer of the binary log required during replication, both the master
and the slave must support SSL network connections. If either host does not support SSL connections
(because it has not been compiled or configured for SSL), replication through an SSL connection is not
possible.
Setting Up Replication Using SSL
is up again, you must issue on it the same
3, so that
Slave Master
a master again (for example, because it is the most powerful machine), use the
was unavailable and
Slave 1
RESET MASTER
slaves of Master. Otherwise, they may pick up old
became unavailable.
Master
bind
CHANGE MASTER TO
becomes a slave of
Master
on
Master
you can use
nsupdate
1495
as that issued on
and picks up each
S1 Web Client
was to be the new master. During
before making
Slave
writes from before the
Web Client
to dynamically update your DNS.
1, Slave 2,