Lines Matching refs:item
65 requested keys; after that for each item the server finds it sends to
66 the client one response line with information about the item, and one
67 data block with the item's data; this continues until the server
123 supplied in the request. Sending an 't' flag with a get for an item with 20
143 (relative to an item or to an operation requested by the client) to
237 when the item is retrieved. Clients may use this as a bit field to
243 - <exptime> is expiration time. If it's 0, the item never expires
247 retrieve this item after the expiration time arrives (measured by
248 server time). If a negative value is given the item is immediately
281 - "EXISTS\r\n" to indicate that the item you are trying to store with
284 - "NOT_FOUND\r\n" to indicate that the item you are trying to store
306 Each item sent by the server looks like this:
311 - <key> is the key for the item being sent
319 this specific item.
321 - <data block> is the data for this item.
324 by the server in the item list this means that the server does not
337 - <key> is the key of the item the client wishes the server to delete
347 - "NOT_FOUND\r\n" to indicate that the item with this key was not
357 Commands "incr" and "decr" are used to change data for some item
358 in-place, incrementing or decrementing it. The data for the item is
362 bogus value as if it were 0, leading to confusion). Also, the item
374 - <key> is the key of the item the client wishes to change
377 the item. It is a decimal representation of a 64-bit unsigned integer.
385 - "NOT_FOUND\r\n" to indicate the item with this value was not found
387 - <value>\r\n , where <value> is the new value of the item's data,
402 The "touch" command is used to update the expiration time of an existing item
407 - <key> is the key of the item the client wishes the server to touch
411 item were to expire in 10 seconds, but then was touched with an
412 expiration time of "20", the item would then expire in 20 seconds.
422 - "NOT_FOUND\r\n" to indicate that the item with this key was not
446 Each item sent by the server looks like this:
451 - <key> is the key for the item being sent
459 this specific item.
461 - <data block> is the data for this item.
467 metadata of an item, minus the value.
483 Each of the keys and values are the internal data for the item.
488 fetch = whether an item has been fetched before
508 After this command, the client expects an item to be returned, received as a
513 have the item (because it was never stored, or stored
517 An item sent by the server looks like:
527 - <data block> is the data for this item. Note that the data block is
544 - c: return item cas token
546 - h: return whether item has been hit before as a 0 or 1
548 - l: return time since item was last accessed in seconds
551 - s: return item size token
552 - t: return item TTL remaining in seconds (-1 for unlimited)
553 - u: don't bump the item in the LRU
554 - v: return item value in <data block>
556 These flags can modify the item:
557 - E(token): use token as new CAS value if item is modified
564 - X: item is stale
565 - Z: item has already sent a winning flag
578 - h: return whether item has been hit before as a 0 or 1
579 - l: return time since item was last accessed in seconds
601 the client for normal responses. In the case of metaget, if an item is not
611 - u: don't bump the item in the LRU
613 It is possible to access an item without causing it to be "bumped" to the head
614 of the LRU. This also avoids marking an item as being hit or updating its last
617 - v: return item value in <data block>
622 These flags can modify the item:
623 - E(token): use token as new CAS value if item is modified
625 Normally when an item is created it is given a CAS value from an internal
633 items. If supplied, and metaget does not find the item in cache, it will
634 create a stub item with the key and TTL as supplied. If such an item is
636 have "won" the right to recache an item.
638 The automatically created item has 0 bytes of data.
647 Similar to and can be combined with 'N'. If the remaining TTL of an item is
649 the right to recache an item. This allows refreshing an item before it leads to
654 Similar to "touch" and "gat" commands, updates the remaining TTL of an item if
661 ownership of a cache item. This allows a single client to be atomically
662 notified that it should cache or update an item. Further clients requesting
663 the item can use the existing data block (if valid or stale), retry, wait, or
664 take some other action while the item is missing.
666 This is used when the act of recaching an item can cause undue load on another
669 - X: item is stale
675 This is used when you want to convince clients to recache an item, but it's
678 - Z: item has already sent a winning flag
682 recaching this item. If there is data supplied it may use it, or the client
721 - "EX" (EXISTS), to indicate that the item you are trying to store with
724 - "NF" (NOT_FOUND), to indicate that the item you are trying to store
731 - C(token): compare CAS value when storing item
734 - I: invalidate. set-to-invalid if supplied CAS is older than item's CAS
738 - s: return the size of the stored item on success (ie; new size on append)
739 - T(token): Time-To-Live for item, see "Expiration" above.
749 - C(token): compare CAS value when storing item
751 Similar to the basic "cas" command, only store item if the supplied token
752 matches the current CAS value of the item. When combined with the 'I' flag, a
753 CAS value that is _lower_ than the current value may be accepted, but the item
779 E: "add" command. LRU bump and return NS if item exists. Else
781 A: "append" command. If item exists, append the new value to its data.
782 P: "prepend" command. If item exists, prepend the new value to its data.
783 R: "replace" command. Set only if item already exists.
792 a new item on a miss. If N is supplied, and append reaches a miss, it will
793 create a new item seeded with the data from the append command. It uses the
818 - "NF" (NOT_FOUND), to indicate that the item with this key was not found.
821 stored item.
833 - x: removes the item value, but leaves the item.
843 Instead of removing an item, this will give the item a new CAS value and mark
858 When marking an item as stale with 'I', the 'T' flag can be used to update the
859 TTL as well; limiting the amount of time an item will live while stale and
862 - x: removes the item value, but leaves the item.
864 This deletes the value off of an item (by replacing it with an empty value
865 item atomically). Combined with I this can leave what is effectively a
891 - "NF" (NOT_FOUND), to indicate that the item with this key was not found.
893 - "NS" (NOT_STORED), to indicate that the item was not created as requested
897 stored item.
909 - N(token): auto create item on miss with supplied TTL
929 - N(token): auto create item on miss with supplied TTL
931 Similar to mget, on a miss automatically create the item. A value can be
1095 - The number of microseconds to sleep in between each item checked for
1138 outputs one line for every valid item found in the matching slab classes.
1153 "fetch" (if item has been fetched before).
1166 outputs one line for every valid item found in the matching slab classes.
1229 - "fetchers": Currently emits logs every time an item is fetched internally.
1231 an item before replacing it. Multigets should also emit multiple lines.
1233 - "mutations": Currently emits logs when an item is stored in most cases.
1255 - "deletions": Emits logs when an item is successfully deleted from the
1353 | | | an item being removed. |
1428 | | 64u | Individual sections of an item rescued |
1488 | item_size_max | size_t | maximum item size |
1540 item storage per slab class. The data is returned in the format:
1552 The following item values are defined as of writing.
1562 age_hot Age of the oldest item in HOT LRU.
1563 age_warm Age of the oldest item in WARM LRU.
1564 age Age of the oldest item in the LRU.
1566 evicted Number of times an item had to be evicted from the LRU
1568 evicted_nonzero Number of times an item which had an explicit expire
1571 evicted_time Seconds since the last access for the most recent item
1575 store a new item. This means you are running with -M or
1597 tails to find memory for a new item.
1607 item. mem_requested shows the size of all items within a
1631 'size' is an approximate size of the item, within 32 bytes.
1662 If you want to make a histogram of item sizes for a memcached instance that is
1685 | chunk_size | The amount of space each chunk uses. One item will use |