Comment #23 on issue 260 by edwardqu...@gmail.com: memcached big bug
http://code.google.com/p/memcached/issues/detail?id=260
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6cc5b40 (LWP 11734)]
do_slabs_alloc (id=1, size=size@entry=73) at slabs.c
Comment #22 on issue 260 by dorma...@rydia.net: memcached big bug
http://code.google.com/p/memcached/issues/detail?id=260
what was the original error for that last backtrace?
--
You received this message because this project is configured to send all
issue notifications to this address.
You
Comment #21 on issue 260 by edwardqu...@gmail.com: memcached big bug
http://code.google.com/p/memcached/issues/detail?id=260
It happened again sooner than I expected. I'll see if I can get another one
for you.
(gdb) bt
#0 do_slabs_alloc (id=1, size=size@entry=73) at slabs.c:241
#1 slabs_alloc
Comment #20 on issue 260 by edwardqu...@gmail.com: memcached big bug
http://code.google.com/p/memcached/issues/detail?id=260
This was the first one I did, so I'll check again and get back to you on
that tomorrow (probably).
Sure. I've copied this info to http://linuxproblems.org/memcached/ alo
Comment #19 on issue 260 by dorma...@rydia.net: memcached big bug
http://code.google.com/p/memcached/issues/detail?id=260
Do the backtraces always the look the same for you?
can we get a look at "stats settings" / "stats" / "stats slabs" / "stats
items" as well?
thank you!
--
You received
Comment #18 on issue 260 by edwardqu...@gmail.com: memcached big bug
http://code.google.com/p/memcached/issues/detail?id=260
Here is a back trace. I get the segmentation error every day (fedora 18
memcached-1.4.15-2.fc18.i686)
[root@www2 quick]# gdb memcached 9128
GNU gdb (GDB) Fedora (7.5.1
Memcached is a cache, not storage, you really shouldn't use it as such.
When you set a value in memcached, you have no guarantees whatsoever that
you'll be able to get the value back afterwards. You're guaranteed to get
the latest value set if you get something, and you're guaranteed to not get
a v
Hello Dormando!
Thanks for your reply.
Description and requirements are:
- Memcached will be used a primary storage (i.e. not for caching MySQL).
- It should have failover feature (in case if one server fails all
connections goes to another server).
Basically something like Master-Slave will be
