From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/rep_pri.html | 51 +++++++++++++++++++--------------- 1 file changed, 28 insertions(+), 23 deletions(-) (limited to 'docs/programmer_reference/rep_pri.html') diff --git a/docs/programmer_reference/rep_pri.html b/docs/programmer_reference/rep_pri.html index dc58d591..049c6265 100644 --- a/docs/programmer_reference/rep_pri.html +++ b/docs/programmer_reference/rep_pri.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 12.  - Berkeley DB Replication - Chapter 12.  Berkeley DB Replication  Next
@@ -38,25 +36,32 @@
-

Each database environment included in a replication group must have -a priority, which specifies a relative ordering among the different -environments in a replication group. This ordering is a factor in -determining which environment will be selected as a new master in case -the existing master fails. Both Replication Manager applications and -Base API applications should specify -environment priorities.

-

Priorities are an unsigned integer, but do not need to be unique -throughout the replication group. A priority of 0 means the system can -never become a master. Otherwise, larger valued priorities -indicate a more desirable master. For example, if a replication group -consists of three database environments, two of which are connected by -an OC3 and the third of which is connected by a T1, the third database -environment should be assigned a priority value which is lower than -either of the other two.

-

Desirability of the master is first determined by the client having -the most recent log records. Ties in log records are broken with -the client priority. If both sites have the same log -and the same priority, one is selected at random.

+

+ Each database environment included in a replication group + must have a priority, which specifies a relative ordering + among the different environments in a replication group. This + ordering is a factor in determining which environment will be + selected as a new master in case the existing master fails. + Both Replication Manager applications and Base API + applications should specify environment priorities. +

+

+ Priorities are an unsigned integer, but do not need to be + unique throughout the replication group. A priority of 0 means + the system can never become a master. Otherwise, larger valued + priorities indicate a more desirable master. For example, if a + replication group consists of three database environments, two + of which are connected by an OC3 and the third of which is + connected by a T1, the third database environment should be + assigned a priority value which is lower than either of the + other two. +

+

+ Desirability of the master is first determined by the client + having the most recent log records. Ties in log records are + broken with the client priority. If both sites have the same + log and the same priority, one is selected at random. +

-- cgit v1.2.1