Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 101 by fallenpegasus: Not reading server responses will hang the
server
http://code.google.com/p/memcached/issues/detail?id=101
What steps will reproduce the problem?
1. Issue a lot of commands
2. Don't read the responses
Comment #1 on issue 101 by fallenpegasus: Not reading server responses will
hang the server
http://code.google.com/p/memcached/issues/detail?id=101
Has been reported to community against 1.2.8 as
http://code.google.com/p/memcached/issues/detail?id=101
--
You received this message
Updates:
Status: Started
Owner: trond.norbye
Comment #1 on issue 102 by trond.norbye: PIping null to the server will
crash it
http://code.google.com/p/memcached/issues/detail?id=102
The problem here is that the client will try to spool the data it receives
from the
client
Status: Accepted
Owner: trond.norbye
Labels: Type-Enhancement Priority-Low Usability
New issue 103 by trond.norbye: Inconsistent use of ERROR and CLIENT_ERROR
http://code.google.com/p/memcached/issues/detail?id=103
According to protocol.txt the following strings are used for errors:
- ERROR\r
Comment #2 on issue 102 by dsallings: PIping null to the server will crash
it
http://code.google.com/p/memcached/issues/detail?id=102
This doesn't seem right. Doesn't that make multiget not work, or am I not
understanding?
I think the first, say, 16 bytes needs to look like a valid
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 104 by benctsui: stats bug for cmd_get
http://code.google.com/p/memcached/issues/detail?id=104
What steps will reproduce the problem?
1. telnet into memcached
2. type stats
3. cmd_get will be the same as get_hits
What
Updates:
Status: Fixed
Comment #3 on issue 102 by dsallings: PIping null to the server will crash
it
http://code.google.com/p/memcached/issues/detail?id=102
Latest changes look good. Thanks! :)
--
You received this message because you are listed in the owner
or CC fields
Comment #4 on issue 3 by dsallings: Textual delete command w/ expire time
noreply in binary protocol version
http://code.google.com/p/memcached/issues/detail?id=3
I've pushed a branch for this (finally... this is an old one).
--
You received this message because you are listed
Updates:
Status: Started
Comment #2 on issue 54 by dsallings: init script missing LSB section
http://code.google.com/p/memcached/issues/detail?id=54
I pushed a branch with Monty's change. The other change requires patching
files that
are not in the distribution (and sounds like
Updates:
Status: Started
Comment #1 on issue 56 by dsallings: Minimum slab size is particular for
growth factor of 2
http://code.google.com/p/memcached/issues/detail?id=56
I agree. This is entirely unexpected behavior and the history doesn't tell
us why
someone made it a special
Updates:
Status: Invalid
Comment #9 on issue 62 by dsallings: Patch: connection queue simplification
http://code.google.com/p/memcached/issues/detail?id=62
I don't think there's a bug here. This looks like something interesting
could come
out of it, but there are a lot of things
Comment #4 on issue 67 by dsallings: TCP/UDP ports need to follow unless
explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67
mdounin -- I do like this idea. We had this discussion in an email thread
and it
turned into a bikeshed. No two participants so far
Updates:
Status: Started
Comment #2 on issue 68 by dsallings: incr/decr resize corruption
http://code.google.com/p/memcached/issues/detail?id=68
I wrote a test that confirms that resizing itself does not cause corruption.
Inspection of the current code doesn't show how this would
Updates:
Status: Fixed
Comment #3 on issue 54 by trond.norbye: init script missing LSB section
http://code.google.com/p/memcached/issues/detail?id=54
Pushed
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue
Updates:
Status: Fixed
Comment #3 on issue 68 by trond.norbye: incr/decr resize corruption
http://code.google.com/p/memcached/issues/detail?id=68
I'll close the bug for now, but feel free to reopen the bug if you can
reproduce the
bug with 1.4.2 or newer.
--
You received
Comment #2 on issue 57 by trond.norbye: Second biggest slabclass is always
less than half the biggest
http://code.google.com/p/memcached/issues/detail?id=57
The lru test fails with your patch
--
You received this message because you are listed in the owner
or CC fields of this issue
Comment #2 on issue 56 by trond.norbye: Minimum slab size is particular for
growth factor of 2
http://code.google.com/p/memcached/issues/detail?id=56
LRU test fails with this patch
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #1 on issue 104 by nerdynick: stats bug for cmd_get
http://code.google.com/p/memcached/issues/detail?id=104
I can confirm the reproduction of this with 1.4.2 and Ubuntu 8.04. I tried
this also
with 1 thread and 4 threads. Producing the same results.
Sample data was 99 inserts 149
Comment #3 on issue 57 by dsallings: Second biggest slabclass is always
less than half the biggest
http://code.google.com/p/memcached/issues/detail?id=57
I noticed that last night. Probably should've updated the bug to avoid
having you
waste time on it. :/
I think it's a bug
Updates:
Status: Fixed
Comment #3 on issue 56 by dsallings: Minimum slab size is particular for
growth factor of 2
http://code.google.com/p/memcached/issues/detail?id=56
I think you may have been looking at something including 57. No tests fail
with this
(just ran it locally
Updates:
Owner: trond.norbye
Comment #1 on issue 69 by dsallings: DTrace probes only fire on deletes
which delete things, not those that don't
http://code.google.com/p/memcached/issues/detail?id=69
(No comment was entered for this change.)
--
You received this message because you
Updates:
Status: Fixed
Comment #7 on issue 3 by trond.norbye: Textual delete command w/ expire
time noreply in binary protocol version
http://code.google.com/p/memcached/issues/detail?id=3
(No comment was entered for this change.)
--
You received this message because you
Updates:
Status: Invalid
Comment #2 on issue 69 by trond.norbye: DTrace probes only fire on deletes
which delete things, not those that don't
http://code.google.com/p/memcached/issues/detail?id=69
The probe is only defined to trigger upon success... if you need to figure
out
Updates:
Status: Started
Owner: trond.norbye
Comment #2 on issue 104 by trond.norbye: stats bug for cmd_get
http://code.google.com/p/memcached/issues/detail?id=104
Patch at: http://github.com/trondn/memcached/tree/issue_104
--
You received this message because you are listed
Updates:
Status: Fixed
Comment #3 on issue 104 by dsallings: stats bug for cmd_get
http://code.google.com/p/memcached/issues/detail?id=104
Thanks, Trond.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You
Updates:
Status: Fixed
Comment #3 on issue 90 by trond.norbye: RFE: generic config parser
http://code.google.com/p/memcached/issues/detail?id=90
Pushed to the engine branch.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Updates:
Status: Fixed
Comment #4 on issue 57 by dorma...@rydia.net: Second biggest slabclass is
always less than half the biggest
http://code.google.com/p/memcached/issues/detail?id=57
Fixed the test and pushed this + test fix into my for_143 branch.
--
You received this message
Updates:
Status: Started
Comment #5 on issue 67 by dsallings: TCP/UDP ports need to follow unless
explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
Updates:
Status: Fixed
Comment #7 on issue 96 by trond.norbye: prefix structure memory leak
http://code.google.com/p/memcached/issues/detail?id=96
Fix pushed
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue
Comment #6 on issue 67 by dsallings: TCP/UDP ports need to follow unless
explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67
http://github.com/dustin/memcached/tree/issue_67
I adjusted buildbot to not run two tests on the same host concurrently just
because
Updates:
Status: Fixed
Comment #7 on issue 67 by dsallings: TCP/UDP ports need to follow unless
explicitly told not to
http://code.google.com/p/memcached/issues/detail?id=67
Shipped.
--
You received this message because you are listed in the owner
or CC fields of this issue
Updates:
Owner: dorma...@rydia.net
Comment #1 on issue 99 by dorma...@rydia.net: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
It's been difficult to reproduce this issue. I'll be taking a more careful
look into
it tonight
Comment #2 on issue 99 by dorma...@rydia.net: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
I'm going to punt on this from 1.4.3-rc1 - if we can reproduce and find the
bug
before 1.4.3-final we'll include it, however.
I'm staring
Updates:
Status: Fixed
Comment #3 on issue 98 by dorma...@rydia.net: RPM can't figure out how to
increment versions.
http://code.google.com/p/memcached/issues/detail?id=98
Meant to close this issue, sorry for the spam :(
--
You received this message because you are listed
Comment #4 on issue 82 by gary.steven: run multiple instances of memcached
on one server host
http://code.google.com/p/memcached/issues/detail?id=82
Cant you do this just by specifiying different ports to run on?
I do this today starting 4 instances on a single machine for Developement
Comment #2 on issue 105 by CMPTuOMP3: curr_items stats seem wrong
http://code.google.com/p/memcached/issues/detail?id=105
Thanks for the clarification.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may
Comment #2 on issue 100 by robb...@orbis-terrarum.net: 1.4.x: t/binary.t
fails on ARM hardware.
http://code.google.com/p/memcached/issues/detail?id=100
dsallings: any progress on this?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Comment #3 on issue 100 by dsallings: 1.4.x: t/binary.t fails on ARM
hardware.
http://code.google.com/p/memcached/issues/detail?id=100
I'm going to need a login on the box to proceed, I believe. I can't seem
to get
enough information just through buildbot.
--
You received this message
Status: Started
Owner: dsallings
Labels: Type-Defect Priority-Medium
New issue 108 by dsallings: Add partial backwards compatibility for delete
with timeout 0
http://code.google.com/p/memcached/issues/detail?id=108
We have accidentally had some backwards compatibility for deletion
Status: New
Owner:
Labels: Type-Enhancement
New issue 109 by steve.yen: efficient, rough top-N hot items
http://code.google.com/p/memcached/issues/detail?id=109
A stats command enhancement that provides information on the hottest N
keys/items in memcached would be useful.
Here's one idea
Comment #6 on issue 82 by mailsort: run multiple instances of memcached on
one server host
http://code.google.com/p/memcached/issues/detail?id=82
I have 6 memcache servers running on my vps with different ports since
1.4.0. This
is not a defect but your solution is elegant.
--
You
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 111 by selsky: compile errors: array subscript has type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
On Solaris 9-sparc:
$ ./configure --with-libevent=/opt/local
$ make
[...]
gcc -std=gnu99 -DHAVE_CONFIG_H
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 112 by higepon: Please add Erlang memcached client
http://code.google.com/p/memcached/issues/detail?id=112
Will you please add my memcached client for Erlang to ht
tp://code.google.com/p/memcached/wiki/Clients?
http
Updates:
Status: Fixed
Owner: dsallings
Comment #1 on issue 112 by dsallings: Please add Erlang memcached client
http://code.google.com/p/memcached/issues/detail?id=112
Great, thanks. Hoping to get some of these clients corralled in a way as
to make it
clear which ones
Comment #2 on issue 112 by higepon: Please add Erlang memcached client
http://code.google.com/p/memcached/issues/detail?id=112
Thanks.
In the meantime, having a comprehensive list of what's out there is
useful.
I agree.
--
You received this message because you are listed in the owner
Updates:
Status: Done
Comment #2 on issue 113 by eric.d.lambert: Please add a new java memcached
client
http://code.google.com/p/memcached/issues/detail?id=113
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 114 by ratneshsinghparihar: Multi Set for Client in C#
http://code.google.com/p/memcached/issues/detail?id=114
/// summary
/// This Method is resposible for serializing of a data .
/// It does compression
Updates:
Status: Invalid
Comment #1 on issue 114 by dsallings: Multi Set for Client in C#
http://code.google.com/p/memcached/issues/detail?id=114
I'm not sure what all of this is, but it's not part of the memcached
server. Perhaps
you meant to file a bug against whatever client
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 117 by tacohamers: memcached 1.4.4 segfaults error 6 on CentOS
5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
What steps will reproduce the problem?
1. ./configure --prefix
Comment #2 on issue 111 by brandon.s.ramirez: compile errors: array
subscript has type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
This occurs in Cygwin as well. It occurs with at least 1.4.4 1.4.3.
--
You received this message because you are listed in the owner
or CC
Comment #1 on issue 116 by lindner.profile: update doc/threads.txt
http://code.google.com/p/memcached/issues/detail?id=116
we should just get rid of that doc file, it's very outdated, since threads
are now required as of 1.4.
--
You received this message because you are listed in the owner
Comment #2 on issue 116 by lindner.profile: update doc/threads.txt
http://code.google.com/p/memcached/issues/detail?id=116
fix here..
http://github.com/lindner/memcached/commit/54dfc54f990b43b840c53077525e93921de4a3f4
--
You received this message because you are listed in the owner
or CC
Comment #3 on issue 111 by lindner.profile: compile errors: array subscript
has type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
can you configure with CFLAGS=-save-temps then attach util.i ? I think
this is related to the isspace() macro.
--
You received
Comment #4 on issue 111 by ptiquet: compile errors: array subscript has
type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
I have the same problem. util.i attached is from a Solaris9/sparc system.
Attachments:
util.i 94.4 KB
--
You received this message because
Comment #4 on issue 117 by tacohamers: memcached 1.4.4 segfaults error 6 on
CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
I feel stupid for running CentOS 5.4 someone tell me WHY?
This bug is resolved by installing
libevent-devel-1.3b-1
Updates:
Status: Invalid
Comment #5 on issue 117 by trond.norbye: memcached 1.4.4 segfaults error 6
on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
(No comment was entered for this change.)
--
You received this message because you
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 118 by aavakian: Bad parameter -pthread being used on Solaris
(instead of -pthreads)
http://code.google.com/p/memcached/issues/detail?id=118
What steps will reproduce the problem?
1.
On SunOS (see below for my particular
Comment #1 on issue 118 by trond.norbye: Bad parameter -pthread being used
on Solaris (instead of -pthreads)
http://code.google.com/p/memcached/issues/detail?id=118
According to http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html both
-pthread
and -pthreads should work on SPARC.
What
Comment #5 on issue 111 by lindner.profile: compile errors: array subscript
has type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
fix available in my git repo..
http://github.com/lindner/memcached
--
You received this message because you are listed in the owner
or CC
Comment #4 on issue 118 by aavakian: Bad parameter -pthread being used on
Solaris (instead of -pthreads)
http://code.google.com/p/memcached/issues/detail?id=118
Yep, I was using gcc 3.4.3:
[r...@mem-01.rent.com ~]$ gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
Comment #5 on issue 118 by aavakian: Bad parameter -pthread being used on
Solaris (instead of -pthreads)
http://code.google.com/p/memcached/issues/detail?id=118
From: Avakian, Alain Sent: Mon 1/4/2010 12:09 PM
To: sat...@rent.com
Cc: engt...@rent.com
Subject: Turns out the bug
Comment #6 on issue 118 by aavakian: Bad parameter -pthread being used on
Solaris (instead of -pthreads)
http://code.google.com/p/memcached/issues/detail?id=118
Just wanted to add a quick note that Sun Solaris comes with gcc 3.4.3, and
even
sunfreeware.com only provides gcc-3.4.6
Comment #6 on issue 111 by ptiquet: compile errors: array subscript has
type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
Confirmed fixed here. memcached 1.4.4 now compiles on Sol9/sparc with no
errors with
this change to util.c.
--
You received this message because
Status: Accepted
Owner: dsallings
Labels: Type-Defect Priority-Medium
New issue 119 by dsallings: assertion on objects 1MB
http://code.google.com/p/memcached/issues/detail?id=119
I am using the Windows version of memcached 1.2.5 in production
without issue. I am attempting to upgrade to 1.4.4
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 120 by saroo2603: Failed to write, and not due to blocking:
Resource temporarily unavailable
http://code.google.com/p/memcached/issues/detail?id=120
I have installed microsoft firewall client 4.0.3442 on my windows machine
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 121 by ehetzner: Values with certain keys are not stored on
solaris sparc with libevent 1.4.3
http://code.google.com/p/memcached/issues/detail?id=121
I am experiencing problems using memcached on Solaris (sparc) similar
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 122 by mr.sela: failed to write, and not due blocking: No error
http://code.google.com/p/memcached/issues/detail?id=122
Hi,
i am running memcached 1.4.4 win32 on windows server 64 bit,
i have on this server 4 instances
Comment #8 on issue 60 by maxim.volkov: Compile error with gcc-4.4
http://code.google.com/p/memcached/issues/detail?id=60
A: Yes, patched version worked.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may
Comment #9 on issue 60 by dsallings: Compile error with gcc-4.4
http://code.google.com/p/memcached/issues/detail?id=60
What do you mean by trunk? We've got buildbot builders on gcc 4.4, had
a problem,
and fixed it. This suggests you don't have the fix.
--
You received this message
Comment #1 on issue 110 by martin.grotzke: method for extending the
expiration of an item is needed
http://code.google.com/p/memcached/issues/detail?id=110
There should be a response indicating if the key is actually existing. This
is useful
for the corner case that memcached was restarted
Comment #2 on issue 110 by dsallings: method for extending the expiration
of an item is needed
http://code.google.com/p/memcached/issues/detail?id=110
The response for such a command must indicate the results. noreply
violates anything
related to good protocol processing, but otherwise
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 123 by h...@terminal-consulting.de: Cross compile OpenWrt
http://code.google.com/p/memcached/issues/detail?id=123
What steps will reproduce the problem?
1. Try to issue configure over the OpenWrt Build System
2. Cross Compile
Comment #2 on issue 123 by h...@terminal-consulting.de: Cross compile
OpenWrt
http://code.google.com/p/memcached/issues/detail?id=123
Yes. I'll setup a machine you can login an try to rebuild yourself with the
OpenWrt-SDK-x86.
This includes the toolchain for the release i try to build
Comment #3 on issue 123 by dsallings: Cross compile OpenWrt
http://code.google.com/p/memcached/issues/detail?id=123
That's a great start. I'd love a slave if you can contribute one:
http://code.google.com/p/memcached/wiki/BuildFarm
That way, we can make sure we continue to support your
Comment #5 on issue 48 by a...@enyim.com: binary protocol incr on text
returns success 0
http://code.google.com/p/memcached/issues/detail?id=48
i'm not sure which version includes this fix, but both 1.4.3 and 1.4.4 give
me a status code 0 (SUCCESS) when
trying to increment non numeric
Comment #6 on issue 48 by dsallings: binary protocol incr on text returns
success 0
http://code.google.com/p/memcached/issues/detail?id=48
I see status code 6 and the error text there. 6 == bad value for
incr/decr. I believe this
is correct. This change went in as 1.4.0-rc1-2-gcce46e8
Comment #7 on issue 48 by a...@enyim.com: binary protocol incr on text
returns success 0
http://code.google.com/p/memcached/issues/detail?id=48
yeah, sorry i forgot that the status is supposed to be 16bit not 8.
--
You received this message because you are listed in the owner
or CC fields
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 124 by lionet1: Please add Erlang memcached client
http://code.google.com/p/memcached/issues/detail?id=124
Jumping on the bandwagon of Erlang memcached clients (there are a few
already), here's our
contribution:
http
Comment #10 on issue 60 by i...@quintura.com: Compile error with gcc-4.4
http://code.google.com/p/memcached/issues/detail?id=60
Hello!
I have the same problem.
OS: Suse 11.2
gcc: 4.4.1
# make
make all-recursive
make[1]: Entering directory `/root/memcached-1.4.4'
Making all in doc
make[2
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 125 by i...@quintura.com: Compile error with gcc
http://code.google.com/p/memcached/issues/detail?id=125
What steps will reproduce the problem?
1. ./configure
2. make
What is the expected output? What do you see instead
Comment #1 on issue 125 by dsallings: Compile error with gcc
http://code.google.com/p/memcached/issues/detail?id=125
Do you have configure output from this? We've tested on gcc 4.4 for a
while now and
haven't seen this. While the gcc 4.4 support is a bit of a workaround, it
should detect
Comment #2 on issue 125 by i...@quintura.com: Compile error with gcc
http://code.google.com/p/memcached/issues/detail?id=125
Thanks for answer.
Memcached has compiled correctly with ./configure CC=gcc-4.3.
You can close this ticket.
I have some errors, when i tried with ./configure CC=gcc-4.4
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 126 by WFXiang08: Memory is not de-allocated in
slabs.c/grow_slab_list
http://code.google.com/p/memcached/issues/detail?id=126
Memory is not de-allocated in slabs.c/grow_slab_list
static int grow_slab_list (const unsigned
Updates:
Status: Invalid
Comment #1 on issue 126 by trond.norbye: Memory is not de-allocated in
slabs.c/grow_slab_list
http://code.google.com/p/memcached/issues/detail?id=126
Check the man page for realloc...
--
You received this message because you are listed in the owner
or CC
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 127 by sadao.hiratsuka: incr/decr operations are not thread safe.
http://code.google.com/p/memcached/issues/detail?id=127
incr/decr operations are not thread safe.
- What steps will reproduce the problem?
Please use
Comment #1 on issue 127 by kai...@ak.jp.nec.com: incr/decr operations are
not thread safe.
http://code.google.com/p/memcached/issues/detail?id=127
It seems to me the correct fix is to eliminate inplace incr/decr,
rather than new locks (it possibly damages to scalability).
Also see
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 128 by hackswell: ERROR: You cannot allow the ASCII protocol
while using SASL.
http://code.google.com/p/memcached/issues/detail?id=128
What steps will reproduce the problem?
1. ./configure --enable-sasl --enable-64bit
2
Comment #1 on issue 128 by dsallings: ERROR: You cannot allow the ASCII
protocol while using SASL.
http://code.google.com/p/memcached/issues/detail?id=128
What do you want this to do?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Comment #3 on issue 125 by BenDJ095124367913213465: Compile error with gcc
http://code.google.com/p/memcached/issues/detail?id=125
I'm seeing the same errors as reported above for both
./configure CC=gcc-4.4 ...
./configure CC=gcc-4.5 ...
fwiw,
./configure CC=gcc-4.3 ...
works just fine
Updates:
Status: Fixed
Comment #1 on issue 119 by dsallings: assertion on objects 1MB
http://code.google.com/p/memcached/issues/detail?id=119
Finally found a solution to this problem.
--
You received this message because you are listed in the owner
or CC fields of this issue
Comment #3 on issue 127 by dorma...@rydia.net: incr/decr operations are not
thread safe.
http://code.google.com/p/memcached/issues/detail?id=127
I just tried backporting the patch but I failed at it and it caused a 7%
performance
regression in running that test alone.
So we're going
Comment #4 on issue 127 by dorma...@rydia.net: incr/decr operations are not
thread safe.
http://code.google.com/p/memcached/issues/detail?id=127
Err, I figured it out, but it's still slower and not entirely correct so
we'll have
to figure it more later.
do_add_delta has the global
Updates:
Owner: dormando
Comment #2 on issue 128 by dorma...@rydia.net: ERROR: You cannot allow the
ASCII protocol while using SASL.
http://code.google.com/p/memcached/issues/detail?id=128
I'll take this for 1.4.6. The perl tests should be spawning memcached in
such a way
Updates:
Status: Invalid
Comment #1 on issue 120 by dorma...@rydia.net: Failed to write, and not due
to blocking: Resource temporarily unavailable
http://code.google.com/p/memcached/issues/detail?id=120
Closing this as it isn't a bug.
Please tune your firewall settings; you could
Updates:
Status: WontFix
Comment #1 on issue 109 by dorma...@rydia.net: efficient, rough top-N hot
items
http://code.google.com/p/memcached/issues/detail?id=109
Honestly, doing this out of the LRU is only going to be useful if the
memcached set
traffic is very light. An item isn't
Comment #5 on issue 127 by dorma...@rydia.net: incr/decr operations are not
thread safe.
http://code.google.com/p/memcached/issues/detail?id=127
I'll have to follow this up with another patch as mine's still incomplete,
but I had
a thought...
When items are being sent back to a client
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 129 by techadvise: start-memcached needs to call setsid()
http://code.google.com/p/memcached/issues/detail?id=129
What steps will reproduce the problem?
1. Start a memcached with the included start-memcached perl script from
Comment #1 on issue 129 by lindner.profile: start-memcached needs to call
setsid()
http://code.google.com/p/memcached/issues/detail?id=129
this has been fixed in later versions of memcached 1.2.2 is ancient history.
--
You received this message because you are listed in the owner
or CC
Updates:
Status: Invalid
Comment #2 on issue 129 by dsallings: start-memcached needs to call setsid()
http://code.google.com/p/memcached/issues/detail?id=129
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 130 by mayongzhen: Can memcache deployed on more then one server?
http://code.google.com/p/memcached/issues/detail?id=130
can memcache deployed on more then one server and the servers can
communication each other ?
--
You
1 - 100 of 1290 matches
Mail list logo
