Thank you for your reply
Is there a recommended version for upgrading memcached?
Which is better, 1.4.x latest, 1.5.x latest?
I would like to use a stable version as much as possible, but please give
us your opinion.
2017年11月1日水曜日 3時28分33秒 UTC+9 Dormando:
>
> Hey,
>
> According to your output
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
Note that it could also be that your webapp's threads were all just stuck
waiting to time out on one node. Depending on the client you're using, how
your app is written, it may appear that everything is 'offline', but it's
really just that your app is spending a large amount of time waiting for
on
Hey,
You're saying the process was just suspended and you resumed it with a
signal? Or did it crash and you had to restart it?
I don't recall any major bugs, but that version is very old (Dec 2013), so
support will be limited.
-Dormando
On Mon, 30 Oct 2017, satoshi fujioka wrote:
> Hi.
> We ar
Hi.
We are running 16 memcached with Tomcat's web application as a client.
Suddenly memcached hunged up at 11 o'clock on October 22, 2017.
When an event occurs, all web applications that access memcached
stopped responding.
This event was resolved by resuming the memcached process, Are there
alr
Can you try this patch?
https://github.com/dormando/memcached/commit/724bfb34484347963a27051fed2b4312e189ace3
Either apply it yourself, or just download the raw file:
https://raw.githubusercontent.com/dormando/memcached/724bfb34484347963a27051fed2b4312e189ace3/t/lru-crawler.t
On Wed, 28 May 2014,
I may have misread. When you said the server was sitting at 100% CPU, what
exactly was using all of the CPU? memcached? perl?
On Wed, 28 May 2014, Alex Gemmell wrote:
> Yep, it's 1.4.20. I followed the instructions here
> http://memcached.org/downloads and ran "wget http://memcached.org/latest"
You're completely sure that's the 1.4.20 source tree?
That bug was pretty well fixed...
If you are definitely testing a 1.4.20 binary, here's the way to grab a
trace:
start memcached-debug under gdb:
gdb ./memcached-debug
> handle SIGPIPE nostop noprint pass
> r
T_MEMD_USE_DAEMON="127.0.0.1:11
Hello Dormando,
I am having exactly the same issue but with Memcached 1.4.20.
My server specs are: RHEL 6 (Linux 2.6.32-358.23.2.el6.x86_64), 1880MB RAM,
single core :(
Here are the results of me running "prove -v t/lru-crawler.t". It took
exactly 10m 15s to run before it timed out. I watche
Updates:
Status: Fixed
Comment #2 on issue 366 by dorma...@rydia.net: Memcached 1.4.19 takes 100%
CPU
http://code.google.com/p/memcached/issues/detail?id=366
Nevermind. This should be fixed in 1.4.20, which was just released. Please
try it and re-file if you have trouble.
--
You
Comment #1 on issue 366 by dorma...@rydia.net: Memcached 1.4.19 takes 100%
CPU
http://code.google.com/p/memcached/issues/detail?id=366
Could you attack gdb to a stuck process and get a backtrace?
gdb -p $(pidof memcached)
thread apply all bt
Are you getting timeouts or or it just spinning
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 366 by marek270...@gmail.com: Memcached 1.4.19 takes 100% CPU
http://code.google.com/p/memcached/issues/detail?id=366
What steps will reproduce the problem?
1. Restart httpd.
2. Restart php-fpm.
3. Use memcached in your php
Hello Domando,
I have destroyed the VPS and am re-building again now.I will post the
output of: $ *prove -v t/lru-crawler.t * once I have created another one in
a little while.
You are right it is Ubuntu 12.04.
Cheers.
On Friday, May 2, 2014 1:42:05 PM UTC+12, Dormando wrote:
>
> I don't know.
On Friday, May 2, 2014 1:42:21 PM UTC+12, Wilfred Khalik wrote:
>
> By the way, how much RAM is enough RAM?
>
> On Friday, May 2, 2014 1:28:57 PM UTC+12, Dormando wrote:
>>
>> What's the output of:
>>
>> $ prove -v t/lru-crawler.t
>>
>> How long are the tests taking to run? This has definitely
I don't know. I need to see the output of that program.
On Thu, 1 May 2014, Wilfred Khalik wrote:
> By the way, how RAM is enough RAM?
>
> On Friday, May 2, 2014 1:28:57 PM UTC+12, Dormando wrote:
> What's the output of:
>
> $ prove -v t/lru-crawler.t
>
> How long are the tests
By the way, how RAM is enough RAM?
On Friday, May 2, 2014 1:28:57 PM UTC+12, Dormando wrote:
>
> What's the output of:
>
> $ prove -v t/lru-crawler.t
>
> How long are the tests taking to run? This has definitely been tested on
> ubuntu 12.04 (which is what I assume you meant?), but not somethin
By the way, how RAM is enough RAM?
On Friday, May 2, 2014 1:28:57 PM UTC+12, Dormando wrote:
>
> What's the output of:
>
> $ prove -v t/lru-crawler.t
>
> How long are the tests taking to run? This has definitely been tested on
> ubuntu 12.04 (which is what I assume you meant?), but not somethin
Hello Domando,
I have destroyed the VPS and am re-building again now.I will post the
output of: $ *prove -v t/lru-crawler.t * once I have created another one in
a little while.
You are right it is Ubuntu 12.04.
Cheers.
On Friday, May 2, 2014 1:28:57 PM UTC+12, Dormando wrote:
>
> What's the ou
What's the output of:
$ prove -v t/lru-crawler.t
How long are the tests taking to run? This has definitely been tested on
ubuntu 12.04 (which is what I assume you meant?), but not something with
so little RAM.
On Thu, 1 May 2014, Wilfred Khalik wrote:
> Hi guys,
>
> I get the below failure erro
Hi guys,
I get the below failure error when I run the *make test *command:
Any help would be appreciated.I am running this on 512MB Digital Ocean VPS
by the way on Linux 12.0.4.4 LTS.
Slab Stats 64
Thread stats 200
Global stats 208
Settings 124
Item (no cas) 32
Item (cas) 40
Libevent thread 100
http://code.google.com/p/memcached/wiki/ReleaseNotes1419
Thanks to everyone who helped out with the bugfixes for this release.
Don't want to get my hopes up but I think we're finally running out of
segfaults and refcount leaks (until we go changing more stuff again..).
--
---
You received this
24 matches
Mail list logo
