Lines Matching refs:which
36 data from a server, it must use the length of the data block (which it
45 is a text string which should uniquely identify the data for clients
59 that the client expects one line of response, which will indicate
64 request). The client sends a command line, which includes all the
89 Meta flags are not to be confused with client bitflags, which is an opaque
114 Flags are single character codes, ie 'q' or 'k' or 'I', which adjust the
119 Flags are single character codes, ie 'q' or 'k' or 'O', which adjust the
120 behavior of a command. Flags may contain token arguments, which come after the
126 All commands accept a tokens 'P' and 'L' which are completely ignored. The
131 token to a memcached daemon, which will ignore them.
153 updated on second boundaries, which makes expiration time roughly +/- 1s.
176 of severe server errors, which make it impossible to continue
179 case in which the server closes a connection to a client.
207 First, the client sends a command line which looks like this:
230 "cas" is a check and set operation which means "store this data but
233 - <key> is the key under which the client asks to store the data
252 including the delimiting \r\n. <bytes> may be zero (in which case
273 the reply, which may be:
299 which is received as a text line followed by a data block. After all
376 - <value> is the amount by which the client wants to increase/decrease
439 which is received as a text line followed by a data block. After all
539 Unless the (q) flag was supplied, which suppresses the status code for a miss.
589 example: if pipelining three get commands together, you may not know which
590 response belongs to which without also retrieving the key. If the key is very
710 the reply, which is of the format:
936 An unsigned 64-bit integer which will be seeded as the value on a miss. Must be
970 "mn\r\n" command can be tagged to the end of the chain, which will return an
1013 The slabs automove command enables a background thread which decides on its
1032 - <2> is a highly aggressive mode which causes pages to be moved every time
1043 The traditional model is "flat" mode, which is a single LRU chain per slab
1077 The LRU Crawler is an optional background thread which will walk from the tail
1237 cache. Useful in seeing if items being evicted were actually used, and which
1247 returned to a client while in proxy mode. The conditions which logs are
1282 a number of lines which look like this:
1360 | cas_badval | 64u | Number of CAS reqs for which a key was |
1454 CAVEAT: This section describes statistics which are subject to change in the
1517 | | | which the background thread reads from. |
1536 CAVEAT: This section describes statistics which are subject to change in the
1568 evicted_nonzero Number of times an item which had an explicit expire
1582 expired_unfetched Number of expired items reclaimed from the LRU which
1584 evicted_unfetched Number of valid items evicted from the LRU which were
1586 evicted_active Number of valid items evicted from the LRU which were
1603 Note this will only display information about slabs which exist, so an empty
1615 CAVEAT: This section describes statistics which are subject to change in the
1668 CAVEAT: This section describes statistics which are subject to change in the
1806 items whose update time is earlier than the time at which flush_all
1812 same time (which could e.g. cause a spike in database load with all
1889 requests, both of which are more suitable to TCP transport for reliability