Lines Matching refs:in
21 There are two kinds of data sent in the memcache protocol: text lines
25 unstructured data in exactly the same way it received it, as a byte
26 stream. The server doesn't care about byte order issues in
28 characters that may appear in unstructured data; however, the reader
46 that are interested in storing and retrieving it. Currently the
63 retrieve data corresponding to a set of keys (one or more keys in one
88 of seconds in 30 days); if the number sent by a client is larger than
97 from the server. These error strings come in three types:
105 means some sort of client error in the input line, i.e. the input
106 doesn't conform to the protocol in some way. <error> is a
116 case in which the server closes a connection to a client.
155 - <flags> is an arbitrary 16-bit unsigned integer (written out in
159 Note that in memcached 1.2.1 and higher, flags may be 32-bits, instead
165 items). If it's non-zero (either Unix time or offset in seconds from
171 - <bytes> is the number of bytes in the data block to follow, *not*
172 including the delimiting \r\n. <bytes> may be zero (in which case
243 If some of the keys appearing in a retrieval request are not sent back
244 by the server in the item list this means that the server does not
260 reply. See the note in Storage commands regarding malformed
278 in-place, incrementing or decrementing it. The data for the item is
300 reply. See the note in Storage commands regarding malformed
310 Note that underflow in the "decr" command is caught: if a client tries
311 to decrease the value below 0, the new value will be 0. Overflow in
331 item were to expire in 10 seconds, but then was touched with an
332 expiration time of "20", the item would then expire in 20 seconds.
335 reply. See the note in Storage commands regarding malformed
386 will likely be in flux for several versions. See the wiki/mailing list for
400 worth of free chunks in a slab class. Pages are then re-assigned back into
404 there is an eviction. It is not recommended to run for very long in this
431 - The number of microseconds to sleep in between each item checked for
443 - The maximum number of items to inspect in a slab class per run request. This
460 The special keyword "all" instructs it to crawl all slabs with items in
489 The response format is in "key=value key2=value2" format, for easy parsing.
493 lines back in order.
506 - "mutations": Currently emits logs when an item is stored in most cases.
510 cache. Useful in seeing if items being evicted were actually used, and which
528 kinds of arguments and the data sent are not documented in this version
546 <value> is the data. The following is the list of all names sent in
575 | rejected_connections | 64u | Conns rejected in maxconns_fast mode |
592 | delete_hits | 64u | Number of deletion reqs resulting in |
625 | | 64u | Number of microseconds in maxconns. |
655 | slab_reassign_rescues | 64u | Items rescued from eviction in page move |
658 | | | (due to no free memory in slab) |
677 CAVEAT: This section describes statistics which are subject to change in the
684 Note that these are not guaranteed to return in any specific order and
691 | maxbytes | size_t | Maximum number of bytes allows in this cache |
715 | hash_algorithm | char | Hash table algorithm in use |
740 CAVEAT: This section describes statistics which are subject to change in the
744 item storage per slab class. The data is returned in the format:
760 number Number of items presently stored in this class. Expired
762 number_hot Number of items presently stored in the HOT LRU.
763 number_warm Number of items presently stored in the WARM LRU.
764 number_cold Number of items presently stored in the COLD LRU.
765 number_noexp Number of items presently stored in the NOEXP class.
766 age Age of the oldest item in the LRU.
788 lrutail_reflocked Number of items found to be refcount locked in the
803 CAVEAT: This section describes statistics which are subject to change in the
807 general size and count of all items stored in the cache.
811 The data is returned in the following format:
824 factor would save memory overhead. For example: generating more classes in the
826 most of your items are less than 200 bytes in size.
861 CAVEAT: This section describes statistics which are subject to change in the
866 information along with some totals. The data is returned in the format:
881 | | default is less than or equal to one megabyte in size. |
886 | cmd_set | Total number of set requests storing data in this class. |
898 | mem_requested | Number of bytes requested to be stored in this slab[*]. |
903 * Items are stored in a slab that is the same size or larger than the
906 wasted in a slab class. If you see a lot of waste, consider tuning
914 for new connections. The data is returned in the format:
951 | conn_parse_cmd | The server has received a command and is in the middle |
969 succeeds, and the server sends "OK\r\n" in response (unless "noreply"
972 specified. After invalidation none of the items will be returned in
981 The intent of flush_all with a delay, was that in a setting where you
984 same time (which could e.g. cause a spike in database load with all
986 have been found in the memcached daemon).
988 The delay option allows you to have them reset in e.g. 10 second
1009 and the server sends "OK\r\n" in response (unless "noreply" is given
1032 Each UDP datagram contains a simple frame header, followed by data in the
1034 implementation, requests must be contained in a single UDP datagram, but
1041 in network byte order, high byte first):
1045 4-5 Total number of datagrams in this message
1058 datagrams in the message. The client should concatenate the payloads of the
1059 datagrams for a given response in sequence number order; the resulting byte
1060 stream will contain a complete response in the same format as the TCP