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_newsite.html | 82 +++++++++++++++++------------- 1 file changed, 46 insertions(+), 36 deletions(-) (limited to 'docs/programmer_reference/rep_newsite.html') diff --git a/docs/programmer_reference/rep_newsite.html b/docs/programmer_reference/rep_newsite.html index 072cc24f..d9360287 100644 --- a/docs/programmer_reference/rep_newsite.html +++ b/docs/programmer_reference/rep_newsite.html @@ -9,12 +9,12 @@ - +
-

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,36 +36,47 @@
-

To add a new site to the replication group all that is needed -is for the client member to join. Berkeley DB will perform an -internal initialization from the master to the client automatically -and will run recovery on the client to bring it up to date -with the master.

-

For Base API applications, connecting to a -new site in the replication group happens whenever the -DB_ENV->rep_process_message() method returns DB_REP_NEWSITE. The application -should assign the new site a local environment ID number, and all future -messages from the site passed to DB_ENV->rep_process_message() should include that -environment ID number. It is possible, of course, for the application -to be aware of a new site before the return of DB_ENV->rep_process_message() (for -example, applications using connection-oriented protocols are likely to -detect new sites immediately, while applications using broadcast -protocols may not).

-

Regardless, in applications supporting the dynamic addition of database -environments to replication groups, environments joining an existing -replication group may need to provide contact information. (For -example, in an application using TCP/IP sockets, a DNS name or IP -address might be a reasonable value to provide.) This can be done using -the cdata parameter to the DB_ENV->rep_start() method. The information -referenced by cdata is wrapped in the initial contact message -sent by the new environment, and is provided to the existing members of -the group using the rec parameter returned by DB_ENV->rep_process_message(). -If no additional information was provided for Berkeley DB to forward to the -existing members of the group, the data field of the rec -parameter passed to the DB_ENV->rep_process_message() method will be NULL after -DB_ENV->rep_process_message() returns DB_REP_NEWSITE.

-

Replication Manager automatically distributes contact information -using the mechanisms previously described.

+

+ To add a new site to the replication group all that is + needed is for the client member to join. Berkeley DB will + perform an internal initialization from the master to the + client automatically and will run recovery on the client to + bring it up to date with the master. +

+

+ For Base API applications, connecting to a new site in the + replication group happens whenever the DB_ENV->rep_process_message() method + returns DB_REP_NEWSITE. The application should assign the + new site a local environment ID number, and all future + messages from the site passed to DB_ENV->rep_process_message() should include + that environment ID number. It is possible, of course, for the + application to be aware of a new site before the return of + DB_ENV->rep_process_message() (for example, applications using + connection-oriented protocols are likely to detect new sites + immediately, while applications using broadcast protocols may + not). +

+

+ Regardless, in applications supporting the dynamic addition + of database environments to replication groups, environments + joining an existing replication group may need to provide + contact information. (For example, in an application using + TCP/IP sockets, a DNS name or IP address might be a reasonable + value to provide.) This can be done using the cdata parameter to the DB_ENV->rep_start() + method. The information referenced by cdata + is wrapped in the initial contact + message sent by the new environment, and is provided to the + existing members of the group using the rec + parameter returned by DB_ENV->rep_process_message(). If no + additional information was provided for Berkeley DB to forward + to the existing members of the group, the data field of the rec parameter passed to the + DB_ENV->rep_process_message() method will be NULL after DB_ENV->rep_process_message() returns + DB_REP_NEWSITE. +

+

+ Replication Manager automatically distributes contact + information using the mechanisms previously described. +

@@ -84,7 +93,8 @@ using the mechanisms previously described.

Home -  Managing Replication Manager Group Membership +  Managing Replication Manager + group membership
-- cgit v1.2.1