Berkeley DB: DB_ENV->repmgr_set_ack_policy
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++

### DB_ENV->repmgr_set_ack_policy |

`

###

    #include <db.h>

    int
    DB_ENV->repmgr_set_ack_policy(DB_ENV *env, int ack_policy);

    int
    DB_ENV->repmgr_get_ack_policy(DB_ENV *env, int *ack_policyp);

### Description: DB_ENV->repmgr_set_ack_policy

The DB_ENV->repmgr_set_ack_policy method specifies how master and client sites will handle acknowledgment of replication messages which are necessary for "permanent" records. The current implementation requires all sites in a replication group configure the same acknowledgement policy.

The DB_ENV->repmgr_set_ack_policy method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->repmgr_set_ack_policy method may be called at any time during the life of the application.

The DB_ENV->repmgr_set_ack_policy method returns a non-zero error value on failure and 0 on success.

### Parameters

ack_policy
  The ack_policy parameter must be set to one of the following values:
  DB_REPMGR_ACKS_ALL
    The master should wait until all replication clients have acknowledged each permanent replication message.
  DB_REPMGR_ACKS_ALL_PEERS
    The master should wait until all electable peers have acknowledged each permanent replication message (where "electable peer" means a client capable of being subsequently elected master of the replication group).
  DB_REPMGR_ACKS_NONE
    The master should not wait for any client replication message acknowledgments.
  DB_REPMGR_ACKS_ONE
    The master should wait until at least one client site has acknowledged each permanent replication message.
  DB_REPMGR_ACKS_ONE_PEER
    The master should wait until at least one electable peer has acknowledged each permanent replication message (where "electable peer" means a client capable of being subsequently elected master of the replication group).
  DB_REPMGR_ACKS_QUORUM
    The master should wait until it has received acknowledgements from the minimum number of electable peers sufficient to ensure that the effect of the permanent record remains durable if an election is held (where "electable peer" means a client capable of being subsequently elected master of the replication group). This is the default acknowledgement policy.

  Waiting for client acknowledgements is always limited by the DB_REP_ACK_TIMEOUT specified by DB_ENV->rep_set_timeout.

### Description: DB_ENV->repmgr_get_ack_policy

The DB_ENV->repmgr_get_ack_policy method returns the replication manager's client acknowledgment policy.

The DB_ENV->repmgr_get_ack_policy method may be called at any time during the life of the application.

The DB_ENV->repmgr_get_ack_policy method returns a non-zero error value on failure and 0 on success.

### Parameters

ack_policyp
  The DB_ENV->repmgr_get_ack_policy method returns the replication manager's client acknowledgment policy in ack_policyp.

### Class

DB_ENV

### See Also

Replication and Related Methods`

Copyright (c) 1996,2007 Oracle. All rights reserved.