diff options
Diffstat (limited to 'docs/programmer_reference/rep_pri.html')
| -rw-r--r-- | docs/programmer_reference/rep_pri.html | 51 |
1 files changed, 28 insertions, 23 deletions
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 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="rep_id.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Berkeley DB Replication - </th> + <th width="60%" align="center">Chapter 12. Berkeley DB Replication </th> <td width="20%" align="right"> <a accesskey="n" href="rep_app.html">Next</a></td> </tr> </table> @@ -38,25 +36,32 @@ </div> </div> </div> - <p>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.</p> - <p>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.</p> - <p>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.</p> + <p> + 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. + </p> + <p> + 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. + </p> + <p> + 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. + </p> </div> <div class="navfooter"> <hr /> |