Hi all,
I have installed memcached in one of our ubantu server. Also,I have
installed php extension for memcached.
Currently,memcached service status shows running.Also,phpmemcachedAdmin is
visible at the browser but the problem is when I click on see server stats
it gives msg *Server
the same again, right now:
Thread 10 (Thread 0x7fbeab1c1700 (LWP 15511)):
#0 0x7fbeabdc718b in pthread_mutex_trylock () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1 0x004130a8 in item_get ()
#2 0x00409795 in process_command ()
#3 0x0040b61a in drive_machine ()
Hi guys,
I'm getting a rather strange behaviour when I try to issue a get-multi on
memcached, so I'm not sure this is a problem with my understanding of how
the protocol was specified or if it's an issue with either pylibmc or
libmemcached.
What I expect:
As I understand it, for multi-get,
Hey,
Looks like your paste got a bit weird, I see thread 3 twice in the second
one? What were the exact commadns you did for each dump?
Is there any chance you could run the memcached-debug binary from the
build tree and get another stack dump? It might help, though this might be
enough
However, after trying to follow this behaviour in a proxy I'm building, this
order of interactions is not being respected; So, what I did afterwards, to
assert that something strange was going on, was to fire up Wireshark and
listen for memcached requests and
responses. Here's a sample of
Ok, will run memcached-debug on all nodes
and define hashpower to 22\23 on one of them.
Thank you
--
---
You received this message because you are subscribed to the Google Groups
memcached group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Dormando,
So, I've tested Memcached by sending direct byte blocks to it in the order
I expected it to behave, and indeed it works, as you said it would:
https://gist.github.com/diogobaeder/4982425
I have no clue why libmemcached does that switch in the middle, but I
understood what you
Hi,
On Feb 18, 2013, at 6:03 PM, Diogo Baeder diogobae...@gmail.com wrote:
I have no clue why libmemcached does that switch in the middle, but I
understood what you said about not expecting things to happen in an exact
order
Are you sure the data is on the same server? Libmemcached
On Feb 18, 2013, at 6:03 PM, Diogo Baeder diogobae...@gmail.com wrote:
I have no clue why libmemcached does that switch in the middle, but I
understood what you said about not expecting things to happen in an exact
order
Are you sure the data is on the same server? Libmemcached
Yep, agreed, Dormando, not a problem, just different from my initial
expectations. I'll just have to figure out how to use Tornado in my favor,
to build this part, and deal correctly with the asynchronicity. :-)
Cheers!
__
Diogo Baeder
http://diogobaeder.com.br
On Tue,
Guess what: I just built a fake Memcached server, to answer hardcoded
values (same as before) to a get_multi op for pylibmc, with normally
ordered batches (2 reqs, 1 noop, 2 resp, 1 noop), and it worked. So, in the
end, it seems like forcing the ordering is not what is causing me troubles,
it's
11 matches
Mail list logo
