If true, the replication master automatically re-initializes outdated clients (defaults to true).

If true, the replication master sends groups of records to the clients in a single network transfer

If true, the client delays synchronizing to a newly declared master (defaults to false). Clients configured in this way remain unsynchronized until the application calls RepSync()()().

If true, then prevents the use of poll() for polling network events

If true, then prevents the use of SSL for securing messages shared between nodes of a replication group.

If true, Replication Manager automatically runs elections to choose a new master when the old master appears to have become disconnected (defaults to true).

If true, then forces the use of Epoll for polling of network events

Enable simple write forwarding for this site. By default, write operations cannot be performed on a replication client site. This option enables forwarding of simple client put and delete operations to the master site for processing. These operations must use an implicit NULL transaction ID to be forwarded. Any other write operation that specifies a non-NULL transaction throws a DatabaseException. The master must have an open database handle for the database on which a forwarded write operation is being performed. All sites in the replication group should have the same value for this configuration option.

If true, replication only stores the internal information in-memory and cannot keep persistent state across a site crash or reboot. By default, it is false and replication creates files in the environment home directory to preserve the internal information. This configuration flag can only be set before the DatabaseEnvironment is opened.

If true, Berkeley DB method calls that would normally block while clients are in recovery will return errors immediately (defaults to false).

This flag is used to specify the client site in a replication group operating in preferred master mode. A preferred master replication group must contain only two sites, with one site specified as the preferred master site and the other site specified as the client site. The client site in a preferred master replication group takes over temporarily as master when the preferred master site is unavailable.

This flag is used to specify the preferred master site in a replication group operating in preferred master mode. A preferred master replication group must contain only two sites, with one site specified as the preferred master site and the other site specified as the client site. The preferred master site operates as the master site whenever possible.

Specify how master and client sites handle the acknowledgment of replication messages which is necessary for "permanent" records. The current implementation requires all sites in a replication group to configure the same acknowledgement policy.

A list of site configurations.

If true, the Replication Manager observes the strict "majority" rule in managing elections, even in a group with only 2 sites. This means the client in a 2-site group is unable to take over as master if the original master fails or becomes disconnected. (See the Elections section in the Berkeley DB Reference Guide for more information.) Both sites in the replication group should have the same value for this parameter.

The delegate used to transmit data using the replication application's communication infrastructure.

If true, master leases are used for this site (defaults to false).