head 1.2; access; symbols RPM_4_2_1:1.1.1.4 RPM_4_2:1.1.1.4 RPM_4_1_1:1.1.1.4 RPM_4_1:1.1.1.3 RPM_4_0_5:1.1.1.2 RPM_4_0_4:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.57; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2002.01.08.00.30.09; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2002.01.08.00.30.09; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2003.01.18.13.48.58; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2001.12.06.00.08.00; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2003.01.18.14.04.57; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DB_ENV->rep_process_message

DB_ENV->rep_process_message

 APIRef 

#include <db.h>


int
DB_ENV->rep_process_message(DB_ENV *env,
    DBT *control, DBT *rec, int *envid)

Description

The DB_ENV->rep_process_message function processes an incoming replication message sent by a member of the replication group to the local database environment.

The rec and control parameters should reference a copy of the parameters specified by Berkeley DB for the rec and control parameters on the sending environment.

The envid parameter should contain the local identifier that corresponds to the environment that sent the message to be processed (see Replication environment IDs for more information).

For implementation reasons, all incoming replication messages must be processed using the same DB_ENV handle. It is not required that a single thread of control process all messages, only that all threads of control processing messages use the same handle.

The DB_ENV->rep_process_message function may return one of several special conditions:

DB_REP_DUPMASTER
The replication group has more than one master; the application should reconfigure itself as a client by calling the DB_ENV->rep_start function, and then call for an election by calling DB_ENV->rep_elect.

DB_REP_HOLDELECTION
An election is needed, the application should call for an election by calling DB_ENV->rep_elect.

DB_REP_NEWMASTER
A new master has been elected. The memory location referenced by the envid parameter contains the environment ID of the new master. If the recipient of this error return has been made master, it is the application's responsibility to begin acting as the master environment.

DB_REP_NEWSITE
The system received contact information from a new environment. The rec parameter contains the opaque data specified in the cdata parameter to the DB_ENV->rep_start. The application should take whatever action is needed to establish a communication channel with this new environment.

DB_REP_OUTDATED
The current environment's logs are too far out of date with respect to the master to be automatically synchronized. The application should copy over a hot backup of the environment, run recovery, and restart the client.

Otherwise, the DB_ENV->rep_process_message function returns a non-zero error value on failure and 0 on success.

Errors

The DB_ENV->rep_process_message function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->rep_process_message function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

See Also

DB_ENV->rep_start, DB_ENV->rep_elect, DB_ENV->rep_process_message, and DB_ENV->set_rep_transport.

APIRef

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.4 @ text @@ 1.1.1.2 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d29 1 a29 1

The DB_ENV->rep_process_message method processes an incoming replication d40 1 a40 1 processed using the same DB_ENV handle. It is not required that d43 13 a55 9

If a new master has been elected, the DB_ENV->rep_process_message method will return DB_REP_NEWMASTER. The envid parameter contains the environment ID of the new master. If the recipient of this error return has been made master, it is the application's responsibility to begin acting as the master environment.

If the system received contact information from a new environment, the DB_ENV->rep_process_message method will return DB_REP_NEWSITE. The rec parameter contains the opaque data specified in the d59 6 a64 16

If the replication group has more than one master, the DB_ENV->rep_process_message method will return DB_REP_DUPMASTER. The application should reconfigure itself as a client by calling the DB_ENV->rep_start method, and then call for an election by calling DB_ENV->rep_elect.

If an election is needed, the DB_ENV->rep_process_message method will return DB_REP_HOLDELECTION. The application should call for an election by calling DB_ENV->rep_elect.

If the current environment's logs are too far out of date with respect to the master to be automatically synchronized, the DB_ENV->rep_process_message method will return DB_REP_OUTDATED. The application should copy over a hot backup of the environment, run recovery, and restart the client.

Otherwise, the DB_ENV->rep_process_message method returns a non-zero error value on failure and 0 on success. d66 4 a69 6

The DB_ENV->rep_process_message method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->rep_process_message method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV d71 5 a75 1 Replication and Related Methods @ 1.1.1.3 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d30 1 a30 1

The DB_ENV->rep_process_message function processes an incoming replication d41 1 a41 1 processed using the same DB_ENV handle. It is not required that d44 9 a52 13

The DB_ENV->rep_process_message function may return one of several special conditions:

DB_REP_DUPMASTER
The replication group has more than one master; the application should reconfigure itself as a client by calling the DB_ENV->rep_start function, and then call for an election by calling DB_ENV->rep_elect.

DB_REP_HOLDELECTION
An election is needed, the application should call for an election by calling DB_ENV->rep_elect.

DB_REP_NEWMASTER
A new master has been elected. The memory location referenced by the envid parameter contains the environment ID of the new master. If the recipient of this error return has been made master, it is the application's responsibility to begin acting as the master environment.

DB_REP_NEWSITE
The system received contact information from a new environment. The rec parameter contains the opaque data specified in the d56 16 a71 6

DB_REP_OUTDATED
The current environment's logs are too far out of date with respect to the master to be automatically synchronized. The application should copy over a hot backup of the environment, run recovery, and restart the client.

Otherwise, the DB_ENV->rep_process_message function returns a non-zero error value on failure and 0 on success. d73 6 a78 4

The DB_ENV->rep_process_message function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->rep_process_message function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d80 1 a80 5 DB_ENV->rep_start, DB_ENV->rep_elect, DB_ENV->rep_process_message, and DB_ENV->set_rep_transport. @ 1.1.1.4 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d29 1 a29 1

The DB_ENV->rep_process_message method processes an incoming replication d40 1 a40 1 processed using the same DB_ENV handle. It is not required that d43 13 a55 9

If a new master has been elected, the DB_ENV->rep_process_message method will return DB_REP_NEWMASTER. The envid parameter contains the environment ID of the new master. If the recipient of this error return has been made master, it is the application's responsibility to begin acting as the master environment.

If the system received contact information from a new environment, the DB_ENV->rep_process_message method will return DB_REP_NEWSITE. The rec parameter contains the opaque data specified in the d59 6 a64 16

If the replication group has more than one master, the DB_ENV->rep_process_message method will return DB_REP_DUPMASTER. The application should reconfigure itself as a client by calling the DB_ENV->rep_start method, and then call for an election by calling DB_ENV->rep_elect.

If an election is needed, the DB_ENV->rep_process_message method will return DB_REP_HOLDELECTION. The application should call for an election by calling DB_ENV->rep_elect.

If the current environment's logs are too far out of date with respect to the master to be automatically synchronized, the DB_ENV->rep_process_message method will return DB_REP_OUTDATED. The application should copy over a hot backup of the environment, run recovery, and restart the client.

Otherwise, the DB_ENV->rep_process_message method returns a non-zero error value on failure and 0 on success. d66 4 a69 6

The DB_ENV->rep_process_message method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->rep_process_message method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV d71 5 a75 1 Replication and Related Methods @