Hey,
According to your output you're running 1.4.16, which was not affected by
the bug in 1.4.20.
Did you check `dmesg` or syslogs to be sure the process didn't run out of
memory and get killed?
You should consider upgrading if you can, since I can't support a version
that old anyway.
-Dormando
Thank you for your reply. Yes, we had to restart the memcached process.
Release note 1.4.20
https://github.com/memcached/memcached/wiki/ReleaseNotes 1420 I thought
that I might have encountered this problem. Do you know this problem?
Certainly the version is old, we are considering upgrading.
Thank you for your reply. When problems occurred, since the web application
did not respond, the subsequent request was blocked. Timeout set to 10
seconds. However, no timeout occurred, and there was no response. The
memcached client is using "memcached client for java v2.5.1". Do you have
any
Thank you for your reply.
That's right, I had to restart the memcached process.
Release note for 1.4.20
https://github.com/memcached/memcached/wiki/ReleaseNotes 1420
I thought that I might have encountered this problem. Do you know this problem?
Certainly the version is old, we are considerin
hi,
actually my boss wanted me to use SeaStar framework because of the good
benchmark results they have achieved ... but as you guessed I am just
trying to understand it's methods and make its tools regarding my project
needs up and running ... that I have n't succeeded so far for memcached
to
No idea what that is.
Do you really need something that fast (which doesn't seem to be
supported?). Thread scalability's gotten better in mainline since they did
their bench, it seems.
If you're just playing around, sorry. I'm not familiar with the thing.
On Mon, 30 Oct 2017, llzz22.55s...@gmail
