Lines Matching refs:be
37 will be provided with) to determine where the data block ends, and not
89 Meta flags are not to be confused with client bitflags, which is an opaque
127 arguments to 'P' and 'L' can be used as hints or path specifications to a
144 the server. In all such cases, the actual value sent may either be
149 that, the server will consider it to be real Unix time value rather
159 Each command sent by a client may be answered with an error string
201 - "CLIENT_ERROR [message]\r\n" will be returned if authentication fails for
239 Note that in memcached 1.2.1 and higher, flags may be 32-bits, instead
244 (although it may be deleted from the cache to make place for other
246 current time), it is guaranteed that clients will not be able to
252 including the delimiting \r\n. <bytes> may be zero (in which case
273 the reply, which may be:
343 The response line to this command can be one of:
383 The response will be one of:
391 to decrease the value below 0, the new value will be 0. Overflow in
395 guaranteed to decrement its returned length. The number MAY be
418 The response line to this command can be one of:
473 key will also be base64 encoded.
492 Others may be added.
508 After this command, the client expects an item to be returned, received as a
528 optional, requiring the 'v' flag to be supplied.
562 These extra flags can be added to the response:
595 Opaque tokens may be up to 32 bytes in length, and are a string similar to
613 It is possible to access an item without causing it to be "bumped" to the head
619 The data block for a metaget response is optional, requiring this flag to be
643 Can be combined with CAS flags to gate the update further.
647 Similar to and can be combined with 'N'. If the remaining TTL of an item is
657 These extra flags can be added to the response:
660 When combined with N or R flags, a client may be informed they have "won"
661 ownership of a cache item. This allows a single client to be atomically
671 Items can be marked as stale by the metadelete command. This indicates to the
672 client that an object needs to be updated, and that it should make a decision
707 is assumed to be 0 length.
753 CAS value that is _lower_ than the current value may be accepted, but the item
754 will be marked as "stale", returning the X flag with mget requests.
760 - I: invalid. set-to-invalid if CAS is older than it should be.
772 would start with "HD" will not be sent. Any other code, such as "EX"
773 (EXISTS) will still be returned.
794 TTL from N instead of T to be consistent with the usage of N in other
839 Can be used to only delete or mark-stale if a supplied CAS value matches.
845 be supplied an 'X' flag to show the data is stale and needs to be recached.
858 When marking an item as stale with 'I', the 'T' flag can be used to update the
860 waiting to be recached.
925 Can be used to only incr/decr if a supplied CAS value matches. A new CAS value
931 Similar to mget, on a miss automatically create the item. A value can be
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
980 instance has hit its limit. It might be desirable to have memory laid out
991 The response line could be one of:
1002 - "NOTFULL [message]" dest class must be full to move new pages to it
1015 will likely be in flux for several versions. See the wiki/mailing list for
1018 The automover can be enabled or disabled at runtime with this command.
1024 The response should always be "OK\r\n"
1032 - <2> is a highly aggressive mode which causes pages to be moved every time
1062 and be unevictable until they naturally expire or are otherwise deleted or
1065 The response line could be one of:
1087 The response line could be one of:
1099 The response line could be one of:
1111 The response line could be one of:
1121 head. The crawler cannot be stopped or restarted until it completes the
1127 The response line could be one of:
1144 more likely all items will be visited once as LRU reordering and locking can
1145 cause frequently accessed items to be missed.
1155 The response line could be one of:
1170 more likely all items will be visited once as LRU reordering and locking can
1171 cause frequently accessed items to be missed.
1178 The response line could be one of:
1207 - Turn connection into a watcher. Options can be stacked and are
1208 space-separated. Logs will be sent to the watcher until it disconnects.
1210 The response line could be one of:
1218 number of the log line. Given how logs are collected internally they may be
1219 printed out of order. If this is important the GID may be used to put log
1234 Shows errors for most cases when items cannot be stored.
1248 written here may be influenced by configuration.
1256 cache using `delete` or `md` commands. delete misses wouldn't be logged
1412 | | | Items can be evicted to avoid OOM errors. |
1436 | | | retry before page can be moved. |
1439 | | | deletion before page can be moved. |
1441 | log_worker_written | 64u | Logs written by a worker, to be picked up |
1462 this list may not be exhaustive. Otherwise, this returns like any
1528 | | NOTE: uring may be used if kernel too old |
1565 mem_requested Number of bytes requested to be stored in this LRU[*]
1566 evicted Number of times an item had to be evicted from the LRU
1569 time set had to be evicted from the LRU before it
1590 lrutail_reflocked Number of items found to be refcount locked in the
1641 In 1.4.27 and after, this feature must be manually enabled.
1643 It can be enabled at starttime with "-o track_sizes"
1654 NOTE: From 1.4.27 to 1.6.24 this feature could be enabled or disabled at
1657 it would make the feature too slow to be usable.
1659 The feature can still be enabled at start time via `-o track_sizes` and has a
1722 The following "stat" keywords may be present:
1738 | | this will be the number of seconds the current |
1742 The value of the "state" stat may be one of the following:
1800 specified. After invalidation none of the items will be returned in
1807 was set to be executed to be ignored for retrieval purposes.
1825 be released back to the OS asynchronously.
1832 may be specified as the single argument to instead trigger a graceful shutdown
1833 with SIGUSR1. The shutdown command is disabled by default, and can be enabled
1880 delivery, so should only be used for operations that aren't required to
1882 incomplete response can simply be treated as a cache miss.
1886 implementation, requests must be contained in a single UDP datagram, but
1898 6-7 Reserved for future use; must be 0
1900 The request ID is supplied by the client. Typically it will be a
1906 ID are probably delayed responses to an earlier request and should be