Edit File - File Manager

Edit File: rep_stat.html

<html>
<head>
<title>Berkeley DB: DB_ENV-&gt;rep_stat</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td>
DB_ENV-&gt;rep_stat
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a>
<a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a></td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>
#include &lt;db.h&gt;

int
DB_ENV-&gt;rep_stat(DB_ENV *env, DB_REP_STAT **statp, u_int32_t flags);

int
DB_ENV-&gt;rep_stat_print(DB_ENV *env, u_int32_t flags);
</pre>
<hr size=1 noshade>
Description: DB_ENV-&gt;rep_stat
The DB_ENV-&gt;rep_stat method returns the replication subsystem statistics.
The DB_ENV-&gt;rep_stat method creates a statistical structure of type
DB_REP_STAT and copies a pointer to it into a user-specified memory
location.
Statistical structures are stored in allocated memory. If application-specific allocation
routines have been declared (see <a href="../../db4-devel-4.7.25/api_c/env_set_alloc.html">DB_ENV-&gt;set_alloc</a> for more
information), they are used to allocate the memory; otherwise, the
standard C library malloc(3) is used. The caller is
responsible for deallocating the memory. To deallocate the memory, free
the memory reference; references inside the returned memory need not be
individually freed.
The following DB_REP_STAT fields will be filled in:
 
u_int32_t st_bulk_fills;<ul compact><li>The number of times the bulk buffer filled up, forcing the buffer content
to be sent.</ul>
u_int32_t st_bulk_overflows;<ul compact><li>The number of times a record was bigger than the entire bulk buffer,
and therefore had to be sent as a singleton.</ul>
u_int32_t st_bulk_records;<ul compact><li>The number of records added to a bulk buffer.</ul>
u_int32_t st_bulk_transfers;<ul compact><li>The number of bulk buffers transferred (via a call to the
application's send function).</ul>
u_int32_t st_client_rerequests;<ul compact><li>The number of times this client site received a "re-request" message,
indicating that a request it previously sent to another client could
not be serviced by that client. (Compare to
st_client_svc_miss.)</ul>
u_int32_t st_client_svc_miss;<ul compact><li>The number of "request" type messages received by this client that
could not be processed, forcing the originating requester to try sending
the request to the master (or another client).</ul>
u_int32_t st_client_svc_req;<ul compact><li>The number of "request" type messages received by this client.
("Request" messages are usually sent from a client to the master, but a
message marked with the <a href="../../db4-devel-4.7.25/api_c/rep_transport.html#DB_REP_ANYWHERE">DB_REP_ANYWHERE</a> flag in the invocation
of the application's send function may be sent to another client
instead.)</ul>
u_int32_t st_dupmasters;<ul compact><li>The number of duplicate master conditions originally detected at this site.</ul>
u_int32_t st_egen;<ul compact><li>The current election generation number.</ul>
u_int32_t st_election_cur_winner;<ul compact><li>The election winner.</ul>
u_int32_t st_election_gen;<ul compact><li>The election generation number.</ul>
DB_LSN st_election_lsn;<ul compact><li>The maximum LSN of election winner.</ul>
u_int32_t st_election_nsites;<ul compact><li>The number sites responding to this site during the last election.</ul>
u_int32_t st_election_nvotes;<ul compact><li>The number of votes required in the last election.</ul>
u_int32_t st_election_priority;<ul compact><li>The election priority.</ul>
u_int32_t st_election_sec;<ul compact><li>The number of seconds the last election took (the total election time
is st_election_sec plus st_election_usec).</ul>
u_int32_t st_election_status;<ul compact><li>The current election phase (0 if no election is in progress).</ul>
u_int32_t st_election_tiebreaker;<ul compact><li>The election tiebreaker value.</ul>
u_int32_t st_election_usec;<ul compact><li>The number of microseconds the last election took (the total election
time is st_election_sec plus st_election_usec).</ul>
u_int32_t st_election_votes;<ul compact><li>The number of votes received in the last election.</ul>
u_int32_t st_elections;<ul compact><li>The number of elections held.</ul>
u_int32_t st_elections_won;<ul compact><li>The number of elections won.</ul>
u_int32_t st_env_id;<ul compact><li>The current environment ID.</ul>
u_int32_t st_env_priority;<ul compact><li>The current environment priority.</ul>
u_int32_t st_gen;<ul compact><li>The current generation number.</ul>
u_int32_t st_log_duplicated;<ul compact><li>The number of duplicate log records received.</ul>
u_int32_t st_log_queued;<ul compact><li>The number of log records currently queued.</ul>
u_int32_t st_log_queued_max;<ul compact><li>The maximum number of log records ever queued at once.</ul>
u_int32_t st_log_queued_total;<ul compact><li>The total number of log records queued.</ul>
u_int32_t st_log_records;<ul compact><li>The number of log records received and appended to the log.</ul>
u_int32_t st_log_requested;<ul compact><li>The number of times log records were missed and requested.</ul>
u_int32_t st_master;<ul compact><li>The current master environment ID.</ul>
u_int32_t st_master_changes;<ul compact><li>The number of times the master has changed.</ul>
u_int32_t st_max_lease_sec;<ul compact><li>The number of seconds of the longest lease (the total lease time
is st_max_lease_sec plus st_max_lease_usec).</ul>
u_int32_t st_max_lease_usec;<ul compact><li>The number of microseconds of the longest lease (the total lease
time is st_max_lease_sec plus st_max_lease_usec).</ul>
DB_LSN st_max_perm_lsn;<ul compact><li>The LSN of the maximum permanent log record, or 0 if there are no
permanent log records.</ul>
u_int32_t st_msgs_badgen;<ul compact><li>The number of messages received with a bad generation number.</ul>
u_int32_t st_msgs_processed;<ul compact><li>The number of messages received and processed.</ul>
u_int32_t st_msgs_recover;<ul compact><li>The number of messages ignored due to pending recovery.</ul>
u_int32_t st_msgs_send_failures;<ul compact><li>The number of failed message sends.</ul>
u_int32_t st_msgs_sent;<ul compact><li>The number of messages sent.</ul>
u_int32_t st_newsites;<ul compact><li>The number of new site messages received.</ul>
DB_LSN st_next_lsn;<ul compact><li>In replication environments configured as masters, the next LSN expected.
In replication environments configured as clients, the next LSN to be used.</ul>
u_int32_t st_next_pg;<ul compact><li>The next page number we expect to receive.</ul>
u_int32_t st_nsites;<ul compact><li>The number of sites used in the last election.</ul>
u_int32_t st_nthrottles;<ul compact><li>Transmission limited. This indicates the number of times that data
transmission was stopped to limit the amount of data sent in response
to a single call to <a href="../../db4-devel-4.7.25/api_c/rep_message.html">DB_ENV-&gt;rep_process_message</a>.</ul>
u_int32_t st_outdated;<ul compact><li>The number of outdated conditions detected.</ul>
u_int32_t st_pg_duplicated;<ul compact><li>The number of duplicate pages received.</ul>
u_int32_t st_pg_records;<ul compact><li>The number of pages received and stored.</ul>
u_int32_t st_pg_requested;<ul compact><li>The number of pages missed and requested from the master.</ul>
u_int32_t st_startsync_delayed;<ul compact><li>The number of times the client had to delay the start of a
cache flush operation (initiated by the master for an impending
checkpoint) because it was missing some previous log record(s).</ul>
u_int32_t st_startup_complete;<ul compact><li>The client site has completed its startup procedures and is now
handling live records from the master.</ul>
u_int32_t st_status;<ul compact><li>The current replication mode. Set to <a href="../../db4-devel-4.7.25/api_c/repmgr_start.html#DB_REP_MASTER">DB_REP_MASTER</a> if the
environment is a replication master, <a href="../../db4-devel-4.7.25/api_c/repmgr_start.html#DB_REP_CLIENT">DB_REP_CLIENT</a> if the
environment is a replication client, or 0 if replication is not
configured.</ul>
u_int32_t st_txns_applied;<ul compact><li>The number of transactions applied.</ul>
DB_LSN st_waiting_lsn;<ul compact><li>The LSN of the first log record we have after missing log records
being waited for, or 0 if no log records are currently missing.</ul>
u_int32_t st_waiting_pg;<ul compact><li>The page number of the first page we have after missing pages
being waited for, or 0 if no pages are currently missing.</ul>
 
The DB_ENV-&gt;rep_stat method may not be called before the <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> method is called.
The DB_ENV-&gt;rep_stat method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 flags<ul compact><li>The flags parameter must be set to 0 or
the following value:
 
<a name="DB_STAT_CLEAR">DB_STAT_CLEAR</a><ul compact><li>Reset statistics after returning their values.</ul>
 </ul>
 statp<ul compact><li>The statp parameter references memory into which
a pointer to the allocated statistics structure is copied.</ul> 
 
 Errors
The DB_ENV-&gt;rep_stat method
may fail and return one of the following non-zero errors:
 
EINVAL<ul compact><li>An
invalid flag value or parameter was specified.</ul>
 
<hr size=1 noshade>
Description: DB_ENV-&gt;rep_stat_print
The DB_ENV-&gt;rep_stat_print method displays the
replication subsystem statistical information, as described for the DB_ENV-&gt;rep_stat method.
The information is printed to a specified output channel (see the
<a href="../../db4-devel-4.7.25/api_c/env_set_msgfile.html">DB_ENV-&gt;set_msgfile</a> method for more information), or passed to an
application callback function (see the <a href="../../db4-devel-4.7.25/api_c/env_set_msgcall.html">DB_ENV-&gt;set_msgcall</a> method for
more information).
The DB_ENV-&gt;rep_stat_print method may not be called before the <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> method is called.
The DB_ENV-&gt;rep_stat_print method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 flags<ul compact><li>The flags parameter must be set to 0 or by bitwise inclusively OR'ing together one
or more of the following values:
 
<a name="DB_STAT_ALL">DB_STAT_ALL</a><ul compact><li>Display all available information.</ul>
<a name="DB_STAT_CLEAR">DB_STAT_CLEAR</a><ul compact><li>Reset statistics after displaying their values.</ul>
 </ul>
 
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a>
 See Also
<a href="../../db4-devel-4.7.25/api_c/rep_list.html">Replication and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a><a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager