search

Jdesk / memcached

Automatically exported from code.google.com/p/memcached
0 stars 0 forks source link

DTrace probes only fire on deletes which delete things, not those that don't #69

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set an object
2. Start the DTrace delete probe
3. Delete the key, then do it again.

What is the expected output? What do you see instead?
Expect to see the probe fire twice, it only fires once.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ingen...@gmail.com on 22 Jul 2009 at 9:24

GoogleCodeExporter commented 9 years ago

Original comment by dsalli...@gmail.com on 29 Oct 2009 at 5:05

GoogleCodeExporter commented 9 years ago 
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...

Original comment by trond.no...@gmail.com on 29 Oct 2009 at 6:46