Thanks. Can you please tell me why you say that I am overengineering. Maybe
I am but I wanted good reasons so that I convince myself. The problem is
some times locks are not happening like say 2-3 times out of 3000 requests,
and I have only 4 reasons so far - 1) get-set race 2) memcache client
Hey,
Memcached can't do that easily right now. You can use the STDOUT logging
but that requires reading everything the server is doing directly.
I started a branch for a better logging situation a few months ago, and am
picking it up to finish over the next few weeks
Real time of offline solutions would be helpful. If I can profile in
background and query it later that is one option. However the only concern
with profiling is that I don't need to profile everything. Or does memcache
do this by default? Can anyone guide me?
On Saturday, June 4, 2016 at
I am trying to troubleshoot an issue which could happen because of get-set
race condition. I can monitor the entire memcache operations but I guess it
is going to be huge because its a small percentage of the DB itself, so I
need to filter only the keys I am interested in. We have a namespacing
