Issue 69 in memcached: DTrace probes only fire on deletes which delete things, not those that don't

[memc...@googlecode.com]

Updates:
Owner: trond.norbye

Comment #1 on issue 69 by dsallings: DTrace probes only fire on deletes
which delete things, not those that don't
http://code.google.com/p/memcached/issues/detail?id=69

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[memc...@googlecode.com]

Updates:
Status: Invalid

Comment #2 on issue 69 by trond.norbye: DTrace probes only fire on deletes

which delete things, not those that don't
http://code.google.com/p/memcached/issues/detail?id=69

The probe is only defined to trigger upon success... if you need to figure
out if it
is a cache hit / miss you need to use the process-command-start and end..

We could create a new set of probes to be more specific, but that should be
filed as
an RFE...