|
NAMEctdb-statistics - CTDB statistics output OVERALL STATISTICSCTDB maintains information about various messages communicated and some of the important operations per node. See the ctdb(1) commands statistics and statisticsreset for displaying statistics. Example: ctdb statisticsCTDB version 1 Current time of statistics : Fri Sep 12 13:32:32 2014 Statistics collected since : (000 01:49:20) Fri Sep 12 11:43:12 2014 CTDB versionVersion of the ctdb protocol used by the node. Current time of statisticsTime when the statistics are generated. This is useful when collecting statistics output periodically for post-processing. Statistics collected sinceTime when ctdb was started or the last time statistics was reset. The output shows the duration and the timestamp. num_clientsNumber of processes currently connected to CTDB's unix socket. This includes recovery daemon, ctdb tool and samba processes (smbd, winbindd). frozen1 if the databases are currently frozen, 0 otherwise. recovering1 if recovery is active, 0 otherwise. num_recoveriesNumber of recoveries since the start of ctdb or since the last statistics reset. client_packets_sentNumber of packets sent to client processes via unix domain socket. client_packets_recvNumber of packets received from client processes via unix domain socket. node_packets_sentNumber of packets sent to the other nodes in the cluster via TCP. node_packets_recvNumber of packets received from the other nodes in the cluster via TCP. keepalive_packets_sentNumber of keepalive messages sent to other nodes. CTDB periodically sends keepalive messages to other nodes. See KeepaliveInterval tunable in ctdb-tunables(7) for more details. keepalive_packets_recvNumber of keepalive messages received from other nodes. nodeThis section lists various types of messages processed which originated from other nodes via TCP. req_call
Number of REQ_CALL messages from the other nodes. reply_call
Number of REPLY_CALL messages from the other nodes. req_dmaster
Number of REQ_DMASTER messages from the other nodes. reply_dmaster
Number of REPLY_DMASTER messages from the other nodes. reply_error
Number of REPLY_ERROR messages from the other nodes. req_message
Number of REQ_MESSAGE messages from the other nodes. req_control
Number of REQ_CONTROL messages from the other nodes. reply_control
Number of REPLY_CONTROL messages from the other nodes. req_tunnel
Number of REQ_TUNNEL messages from the other nodes. clientThis section lists various types of messages processed which originated from clients via unix domain socket. req_call
Number of REQ_CALL messages from the clients. req_message
Number of REQ_MESSAGE messages from the clients. req_control
Number of REQ_CONTROL messages from the clients. req_tunnel
Number of REQ_TUNNEL messages from the clients. timeoutsThis section lists timeouts occurred when sending various messages. call
Number of timeouts for REQ_CALL messages. control
Number of timeouts for REQ_CONTROL messages. traverse
Number of timeouts for database traverse operations. locksThis section lists locking statistics. num_calls
Number of completed lock calls. This includes database locks and record locks. num_current
Number of scheduled lock calls. This includes database locks and record locks. num_pending
Number of queued lock calls. This includes database locks and record locks. num_failed
Number of failed lock calls. This includes database locks and record locks. total_callsNumber of req_call messages processed from clients. This number should be same as client --> req_call. pending_callsNumber of req_call messages which are currently being processed. This number indicates the number of record migrations in flight. childwrite_callsNumber of record update calls. Record update calls are used to update a record under a transaction. pending_childwrite_callsNumber of record update calls currently active. memory_usedThe amount of memory in bytes currently used by CTDB using talloc. This includes all the memory used for CTDB's internal data structures. This does not include the memory mapped TDB databases. max_hop_countThe maximum number of hops required for a record migration request to obtain the record. High numbers indicate record contention. total_ro_delegationsNumber of readonly delegations created. total_ro_revokesNumber of readonly delegations that were revoked. The difference between total_ro_revokes and total_ro_delegations gives the number of currently active readonly delegations. hop_count_bucketsDistribution of migration requests based on hop counts values. Buckets are 0, < 2, < 4, < 8, < 16, < 32, < 64, < 128, < 256, < 512, < 1024, < 2048, < 4096, < 8192, < 16384, ≥ 16384. lock_bucketsDistribution of record lock requests based on time required to obtain locks. Buckets are < 1ms, < 10ms, < 100ms, < 1s, < 2s, < 4s, < 8s, < 16s, < 32s, < 64s, ≥ 64s. locks_latencyThe minimum, the average and the maximum time (in seconds) required to obtain record locks. reclock_ctdbdThe minimum, the average and the maximum time (in seconds) required to check if recovery lock is still held by recovery daemon when recovery mode is changed. This check is done in ctdb daemon. reclock_recdThe minimum, the average and the maximum time (in seconds) required to check if recovery lock is still held by recovery daemon during recovery. This check is done in recovery daemon. call_latencyThe minimum, the average and the maximum time (in seconds) required to process a REQ_CALL message from client. This includes the time required to migrate a record from remote node, if the record is not available on the local node. childwrite_latencyDefault: 0 The minimum, the average and the maximum time (in seconds) required to update records under a transaction. DATABASE STATISTICSCTDB maintains per database statistics about important operations. See the ctdb(1) command dbstatistics for displaying database statistics. Example: ctdb dbstatistics notify_index.tdbDB Statistics: notify_index.tdb DB StatisticsName of the database. ro_delegationsNumber of readonly delegations created in the database. ro_revokesNumber of readonly delegations revoked. The difference in ro_delegations and ro_revokes indicates the currently active readonly delegations. locksThis section lists locking statistics. total
Number of completed lock calls. This includes database locks and record locks. failed
Number of failed lock calls. This includes database locks and record locks. current
Number of scheduled lock calls. This includes database locks and record locks. pending
Number of queued lock calls. This includes database locks and record locks. hop_count_bucketsDistribution of migration requests based on hop counts values. Buckets are 0, < 2, < 4, < 8, < 16, < 32, < 64, < 128, < 256, < 512, < 1024, < 2048, < 4096, < 8192, < 16384, ≥ 16384. lock_bucketsDistribution of record lock requests based on time required to obtain locks. Buckets are < 1ms, < 10ms, < 100ms, < 1s, < 2s, < 4s, < 8s, < 16s, < 32s, < 64s, ≥ 64s. locks_latencyThe minimum, the average and the maximum time (in seconds) required to obtain record locks. Num Hot KeysNumber of contended records determined by hop count. CTDB keeps track of top 10 hot records and the output shows hex encoded keys for the hot records. SEE ALSOctdb(1), ctdbd(1), ctdb-tunables(7), http://ctdb.samba.org/ AUTHORThis documentation was written by Amitay Isaacs, Martin Schwenke COPYRIGHTCopyright © 2007 Andrew Tridgell, Ronnie Sahlberg
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, see http://www.gnu.org/licenses.
|