Memcached running status monitoring

The running status monitoring of Memcached servers can generally be monitored using a dedicated operating system. However, developers can use the statistical commands (stats) supported by memcached protocol in linux. 1. Use telnet to connect to the memcached server telnet10.10.10112112, memcached statistical command, some common statistics or

MeMcAchEdGenerally, a special operating system can be used to monitor the running status of servers. However, General developers can use the statistics supported by the memcached protocol.Command(StatS) in linux.

1. Use teLnEt connects to the memcached Server

Telnet10.10.10.10 11211

2. memcached statistical command

Common statistics or configuration information can be obtained through the stats command. Complete Step 1. Connect to the memcached server and enter the telnet command line and stats. Press enter to obtain the statistics. The statistics include the following information:

P Id: Process id of this server process (memcached server Process number) up Time: Number of secs si NcE the server started (memcache server running time, in seconds) time: current UNIX time according to the server (memcached service machine time, in seconds) version: Version s TrIng of this server (current memcached version number) pointer_size: Default size of pointers on the host OS (generally 32 or 64) (Default pointer address length, according to the operating system, this value can be 32 or 64) rusage_user: Accumulated user time for this process (seconds: microseconds) (accumulative user usage time, accurate to milliseconds) rusage_system: accumulated system time for this process (seconds: microseconds) (accumulative system usage time, accurate to milliseconds) curr_items: Current number of items stored (number of data items currently stored) total_items: total number of items stored since the server started (number of data items stored on this server after startup) bytes: Current number of bytes u SedTo store items (memory occupied by the memcached server, in bytes) curr_connections: Number of open connections (currently open connections) total_connections: total number of connections opened since the server started running (the Number of connections opened by this server after startup) connection_structures: number of connection structures allo CatEd by the server (the connection structure allocated by this server) pai_get: Cumulative number of retri EvalReqs (retrieve request count) cmd _ Set: Cumulative number of storage reqs (Number of storage requests) get_hits: number of keys that have been requested and found present (Number of keys successfully requested, cache hit rate = get_hits/cmd_get * 100%) get_misses: Number of items that have been requested and not found (Number of keys in request failure) delete_misses: Number of deletions reqs for missing keys (Number of keys not hit in data deletion requests) delete_hits: Number of deletion reqs re SuLting in an item being removed. (Number of keys hit by data deletion requests) incr_misses: Number of incr reqs against missing keys. incr_hits: Number of successful incr reqs. decr_misses: Number of decr reqs against missing keys. decr_hits: Number of successful decr reqs. cas_misses: Number of CAS reqs against missing keys. cas_hits: Number of successful CAS reqs. cas_badval: Number of CAS reqs WhichA key was found, but the CAS value did not match. auth_cmds: Number of authentication commands handled, success or failure. auth_errors: Number of failed authentications. evictions: Number of valid items removed from cache FreeMemory for new itemsreclaimed: Number of times an entry was stored using memory from ExPired entry (the number of times new data is stored in the space occupied by expired data, memcached preferentially uses the space occupied by expired data) bytes_read: total number of bytes read by this server from network (Total number of bytes stored) bytes_written: Total number of bytes sent by this server to network (Total number of bytes sent) limit_maxbytes: number of bytes this server is allowed to use for storage. threads: Number of worker threads requested. (see doc/threads.txt) conn_yields: Number of times any connection yielded to another DuE to hitting the-R limit.