Base API Methods

Library Version 11.2.5.3

Library Version 12.1.6.1

- + - +

Base API Methods			Base API methods
Prev	Chapter 12. - Berkeley DB Replication -	Chapter 12. Berkeley DB Replication	Next

@@ -34,12 +32,14 @@

Base API Methods

Base API methods

Base API applications use the following -Berkeley DB methods.

+ Base API applications use the following Berkeley DB + methods. +

@@ -49,9 +49,10 @@ Berkeley DB methods.

- The DB_ENV->rep_set_transport() method configures the replication system's - communications infrastructure. -

+ The DB_ENV->rep_set_transport() method configures the + replication system's communications + infrastructure. +

@@ -59,10 +60,11 @@ Berkeley DB methods.

- The DB_ENV->rep_start() method configures (or reconfigures) an existing database - environment to be a replication master or client. -

+ The DB_ENV->rep_start() method configures (or + reconfigures) an existing database environment to + be a replication master or client. +

@@ -70,18 +72,21 @@ Berkeley DB methods.

- The DB_ENV->rep_process_message() method is used to process incoming messages - from other environments in the replication group. For clients, - it is responsible for accepting log records and updating the - local databases based on messages from the master. For both - the master and the clients, it is responsible for handling - administrative functions (for example, the protocol for dealing - with lost messages), and permitting new clients to join an - active replication group. This method should only be called - after the replication system's communications infrastructure - has been configured via DB_ENV->rep_set_transport(). -

+ The DB_ENV->rep_process_message() method is used to process + incoming messages from other environments in the + replication group. For clients, it is responsible + for accepting log records and updating the local + databases based on messages from the master. For + both the master and the clients, it is responsible + for handling administrative functions (for + example, the protocol for dealing with lost + messages), and permitting new clients to join an + active replication group. This method should only + be called after the replication system's + communications infrastructure has been configured + via DB_ENV->rep_set_transport(). +

@@ -89,12 +94,13 @@ Berkeley DB methods.

- The DB_ENV->rep_elect() method causes the replication group to elect a - new master; it is called whenever contact with the master is - lost and the application wants the remaining sites to select a - new master. -

+ The DB_ENV->rep_elect() method causes the replication + group to elect a new master; it is called whenever + contact with the master is lost and the + application wants the remaining sites to select a + new master. +

@@ -102,11 +108,12 @@ Berkeley DB methods.

- The DB_ENV->set_event_notify() method is needed for applications to - discover important replication-related events, such as the - result of an election and appointment of a new master. -

+ The DB_ENV->set_event_notify() method is needed for + applications to discover important + replication-related events, such as the result of + an election and appointment of a new master. +

@@ -115,9 +122,9 @@ Berkeley DB methods.

- The DB_ENV->rep_set_priority() method configures the local site's priority for - the purpose of elections. -

+ The DB_ENV->rep_set_priority() method configures the local + site's priority for the purpose of elections. +

@@ -125,11 +132,11 @@ Berkeley DB methods.

- This method optionally configures various timeout values. Otherwise - default timeout values as specified in DB_ENV->rep_set_timeout() are - used. -

+ This method optionally configures various + timeout values. Otherwise default timeout values + as specified in DB_ENV->rep_set_timeout() are used. +

@@ -137,18 +144,21 @@ Berkeley DB methods.

- The DB_ENV->rep_set_limit() method imposes an upper bound on the amount of - data that will be sent in response to a single call to - DB_ENV->rep_process_message(). During client recovery, that is, when a replica - site is trying to synchronize with the master, clients may ask - the master for a large number of log records. If it is going - to harm an application for the master message loop to remain - busy for an extended period transmitting records to the - replica, then the application will want to use DB_ENV->rep_set_limit() to - limit the amount of data the master will send before - relinquishing control and accepting other messages. -

+ The DB_ENV->rep_set_limit() method imposes an upper bound on + the amount of data that will be sent in response + to a single call to DB_ENV->rep_process_message(). During client + recovery, that is, when a replica site is trying + to synchronize with the master, clients may ask + the master for a large number of log records. If + it is going to harm an application for the master + message loop to remain busy for an extended period + transmitting records to the replica, then the + application will want to use DB_ENV->rep_set_limit() to limit + the amount of data the master will send before + relinquishing control and accepting other + messages. +

@@ -157,16 +167,24 @@ Berkeley DB methods.

- This method sets a threshold for the minimum and maximum time that - a client waits before requesting retransmission of a missing - message. -

+ This method sets a threshold for the minimum + and maximum time that a client waits before + requesting retransmission of a missing message. +

In addition to the methods previously described, Base API applications -may also call the following methods, as needed: -DB_ENV->rep_stat(), DB_ENV->rep_sync() and DB_ENV->rep_set_config().

+ Base API applications may configure one or more view sites. + A view is a full or partial copy of the replicated data that + does not otherwise participate in the replication group. For + more information, see Replication views. +

+ In addition to the methods previously described, Base API + applications may also call the following methods, as needed: + DB_ENV->rep_stat(), DB_ENV->rep_sync() and DB_ENV->rep_set_config() +