1.4.15

Available at http://memcached.org/ No major fixes, just further performance tuning. Slowly rolling out modernization of the thread scaling, and using this as a base for once-a-month feature pushes that might even actually happen this time! -Dormando

Set operations failing on Memcached 1.4.15

We run 1.4.2 on our cluster though it goes OOM every few days and hence are trying to migrate to a newer build. Release notes of 1.4.15 specifically say that it fixes some OOM cases, so we tried 1.4.15. We noted that around every 40-60 mins, sets would fail in burst. On further digging we found

Re: Set operations failing on Memcached 1.4.15

gt; trying to migrate to a newer build. Release notes of 1.4.15 specifically say > that it fixes some OOM cases, so we tried 1.4.15. We noted that around every > 40-60 mins, sets would fail in burst. > On further digging we found that each such burst corresponds to a spike in > user cp

Re: Set operations failing on Memcached 1.4.15

_time 0 > STAT items:36:outofmemory 0 > STAT items:36:tailrepairs 0 > STAT items:36:reclaimed 0 > STAT items:36:expired_unfetched 0 > STAT items:36:evicted_unfetched 0 > STAT items:37:number 2 > STAT items:37:age 12226 > STAT items:37:evicted 0 > STAT items:37:evicted_nonz

Re: Set operations failing on Memcached 1.4.15

I'm a bit confused: when the CPU usage is spiking is memcached still functioning? Or is it completely hung? those samples you have there are pretty weird. it doesn't appear to be hung on anything? If it's easy for you to reproduce, can you do a little more bisecting? you'

How do I use the "memcached-1.4.15" on windows ?

Hello, I have downloaded "memcached-1.4.15" from www.memcached.org and uninstalled on my windows 8 system (64 bit). How do I set up the memcache server now ? -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To u

Issue 335 in memcached: memcached 1.4.15 crash on CentOS6.3

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 335 by marc.b...@gmail.com: memcached 1.4.15 crash on CentOS6.3 http://code.google.com/p/memcached/issues/detail?id=335 What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead

install libevent and memcached 1.4.15 on Red Hat Linux

Hello All, I am new to the memcached and trying to set this up on my Linux , is it required that memcached should have to be installed only by the root user. -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and

seems a memcached 1.4.15 concurent problem (got wrong value)

Our server is running a memcached cluster with version 1.4.15, and we seem to run into a concurent trouble. In our high concurrent system, the client wanted to get key1(ctw9tjk) but got key2(cqv87p7)'s value, and both key1 and key2 is not found in memcached after then. key1(ctw9tjk) i

Re: How do I use the "memcached-1.4.15" on windows ?

I have the same question.How i will run this on windows systems. Thanks in advance. On Tuesday, 12 March 2013 20:04:36 UTC+5:30, aala...@gmail.com wrote: > > Hello, > > I have downloaded "memcached-1.4.15" from www.memcached.org and > uninstalled on my windows 8

Re: How do I use the "memcached-1.4.15" on windows ?

Here <http://www.codeforest.net/how-to-install-memcached-on-windows-machine>is an intro to how to install memcached on Windows. On Tuesday, March 12, 2013 9:34:36 AM UTC-5, aala...@gmail.com wrote: > > Hello, > > I have downloaded "memcached-1.4.15" from www.memc

Re: Issue 335 in memcached: memcached 1.4.15 crash on CentOS6.3

Comment #1 on issue 335 by dorma...@rydia.net: memcached 1.4.15 crash on CentOS6.3 http://code.google.com/p/memcached/issues/detail?id=335 Hi. By chance are you still seeing this crash? If so, can you try 1.4.16 and run the -debug binary under gdb? The non-debug binary ends up failing

Re: Issue 335 in memcached: memcached 1.4.15 crash on CentOS6.3

Updates: Status: Fixed Comment #2 on issue 335 by dorma...@rydia.net: memcached 1.4.15 crash on CentOS6.3 http://code.google.com/p/memcached/issues/detail?id=335 Please try 1.4.17 (if you ever read this). Closing the bug report otherwise. Not entirely sure if it's fixed (and I

Re: Issue 335 in memcached: memcached 1.4.15 crash on CentOS6.3

Comment #3 on issue 335 by mazhongx...@gmail.com: memcached 1.4.15 crash on CentOS6.3 http://code.google.com/p/memcached/issues/detail?id=335 memcached version 1.4.17 redhat6.4 kernel 2.6.32-358.el6.x86_64 memcached will automatically die, logging the following information more /var/log

Re: Issue 335 in memcached: memcached 1.4.15 crash on CentOS6.3

Comment #4 on issue 335 by dorma...@rydia.net: memcached 1.4.15 crash on CentOS6.3 http://code.google.com/p/memcached/issues/detail?id=335 Can you please run the memcached-debug binary from 1.4.17 compile directory, and get a gdb backtrace of teh crash? -- You received this message

Re: install libevent and memcached 1.4.15 on Red Hat Linux

sudo yum install memcached Regards, __ Filippe Costa Spolti Linux User n°515639 - http://counter.li.org/ filippespo...@gmail.com "Be yourself" On 02/20/2014 03:39 PM, lkra...@gmail.com wrote: Hello

Re: seems a memcached 1.4.15 concurent problem (got wrong value)

day, March 26, 2015 at 9:09:16 PM UTC-7, Feng Liyuan wrote: > > Our server is running a memcached cluster with version 1.4.15, and we seem > to run into a concurent trouble. > > In our high concurrent system, > the client wanted to get key1(ctw9tjk) but got key2(cqv87p7)'s va

Issue 361 in memcached: Segfault in memcached (slabs.c) 1.4.15, patch provided.

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 361 by robert.w...@acm.org: Segfault in memcached (slabs.c) 1.4.15, patch provided. http://code.google.com/p/memcached/issues/detail?id=361 do_slabs_alloc should return NULL due to failure. System information: Red Hat

Re: Issue 361 in memcached: Segfault in memcached (slabs.c) 1.4.15, patch provided.

Comment #1 on issue 361 by dorma...@rydia.net: Segfault in memcached (slabs.c) 1.4.15, patch provided. http://code.google.com/p/memcached/issues/detail?id=361 Hi, I can't accept this. Can you reproduce the crash under 1.4.17 or current master? There was a bug we've fixed in

Re: Issue 361 in memcached: Segfault in memcached (slabs.c) 1.4.15, patch provided.

Comment #2 on issue 361 by dorma...@rydia.net: Segfault in memcached (slabs.c) 1.4.15, patch provided. http://code.google.com/p/memcached/issues/detail?id=361 Yeah, .17: https://github.com/memcached/memcached/commit/cb9c269bd57bb5417b337228cfbb50f4a8769d09 https://github.com/memcached

Re: Issue 361 in memcached: Segfault in memcached (slabs.c) 1.4.15, patch provided.

Updates: Status: Invalid Comment #3 on issue 361 by dorma...@rydia.net: Segfault in memcached (slabs.c) 1.4.15, patch provided. http://code.google.com/p/memcached/issues/detail?id=361 I'm going to close this. *please* let us know if the bug is reproducable under .17 or

memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

Hello, i don't know exactly if it is memcached issue (or OS / libevent) but time to time (~2 days) one or two of 6 memcached servers stops respond \ accept new connections, restart required :( strace output is: Process 20417 attached - interrupt to quit 00:21:15 epoll_wait(3, {}, 32,

Issue 288 in memcached: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 288 by dinst...@163.com: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support http://code.google.com/p/memcached/issues/detail?id=288 What steps will reproduce the problem? 1.we use spymemcached to

Re: memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

> Hello, >    i don't know exactly if it is memcached issue (or OS / libevent) >    but time to time (~2 days) >   one or two of 6 memcached servers stops respond \ accept new connections, > restart required :( >   strace output is: >   > Process 20417 attached - interrupt to quit > 00:21:15 epoll

Re: memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

> That isn't a terrifically high load. Can you do: > > `ls -l /proc/$(pidof memcached)/fd | wc -l` ? just to confirm you aren't > hitting maxconns in a weird way (as netstat doesn't show a ton of stuff > open). > > Do you tend to run your other servers at or near maxconns? > > Your box isn'

Re: memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

> server too far for maxcon or fds limit >   > ls -l /proc/$(pidof memcached)/fd | wc -l > ~1.5K on each server >   > netstat -tpn|grep TIME_WAIT|wc -l > ~100 >   > netstat -tpn|grep ':11211'|wc -l > 1454 >   > cat /proc/net/sockstat > sockets: used 1642 > TCP: inuse 1544 orphan 0 tw 91 alloc 1547

Re: memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

syslog - clean memcached stats from an other memcached_node: array ( 'pid' => '27721', 'uptime' => '496681', 'time' => '1361232187', 'version' => '1.4.15', 'libevent' =

Re: memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

32, 10)   = 0 > epoll_wait(3, {}, 32, 10)   = 0 > epoll_wait(3, {}, 32, 10)   = 0 > epoll_wait(3, {}, 32, 10)   = 0 > epoll_wait(3, {}, 32, 10)   = 0 > epoll_wait(3, {}, 32, 10)   = 0 > epoll_wait(3, {}, 32, 10)  

Re: memcached 1.4.15, high load, infiniti loop on epoll_wait(3, {}, 32, 10) = 0 <0.010073>

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 memcached

Re: Issue 288 in memcached: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support

Comment #1 on issue 288 by dorma...@rydia.net: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support http://code.google.com/p/memcached/issues/detail?id=288 can you run this test with memcached in the foreground with -vvv enabled? does it happen with 1.4.14? I don&#

Re: Issue 288 in memcached: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support

Updates: Status: Invalid Comment #2 on issue 288 by dorma...@rydia.net: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support http://code.google.com/p/memcached/issues/detail?id=288 Closing this bug... please reopen with the information I requested if you&#x

Re: Issue 288 in memcached: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support

Comment #3 on issue 288 by dinst...@163.com: memcached 1.4.13 supports persistent connections, but 1.4.15 does not support http://code.google.com/p/memcached/issues/detail?id=288 I think this problem is the problem of our network, very sorry.

Issue 343 in memcached: memcached-1.4.15 build fails with Intel compiler icc due to missing -std=gnu99 option

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 343 by semenova...@gmail.com: memcached-1.4.15 build fails with Intel compiler icc due to missing -std=gnu99 option http://code.google.com/p/memcached/issues/detail?id=343 What steps will reproduce the problem? 1

Re: Issue 343 in memcached: memcached-1.4.15 build fails with Intel compiler icc due to missing -std=gnu99 option

Comment #1 on issue 343 by dorma...@rydia.net: memcached-1.4.15 build fails with Intel compiler icc due to missing -std=gnu99 option http://code.google.com/p/memcached/issues/detail?id=343 I don't have any icc buildbot hosts right now... can't verify a fix myself. -- You rec

Re: Issue 343 in memcached: memcached-1.4.15 build fails with Intel compiler icc due to missing -std=gnu99 option

Updates: Status: Invalid Comment #2 on issue 343 by dorma...@rydia.net: memcached-1.4.15 build fails with Intel compiler icc due to missing -std=gnu99 option https://code.google.com/p/memcached/issues/detail?id=343 closing this due to age and lack of ability to follow up. if someone