Updates:
Owner: eric.d.lambert
Comment #1 on issue 107 by eric.d.lambert: binary protocol can only parse 1
command within a recieved udp / tcp buffer
http://code.google.com/p/memcached/issues/detail?id=107
(No comment was entered for this change.)
Updates:
Owner: eric.d.lambert
Comment #3 on issue 106 by eric.d.lambert: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
this looks similar to the problem with issue 158, so i'll take a look at
this
Updates:
Status: Fixed
Comment #7 on issue 123 by trond.norbye: Cross compile OpenWrt
http://code.google.com/p/memcached/issues/detail?id=123
The problem in configure was that it tried to use try_run_ifelese, and that
don't work for cross compilation. Update your compiler and try again
Thanks All,
So to use the custom Transconder, I am using
public Future set(String key,int exp,T o,Transcoder
tc) of net.spy.memcached.MemcachedClient
and passing 'new SerializingTranscoder(max)' as the Transcoder object,
with the higher limit I need.
instead of
public Future set(String key,int
Updates:
Status: Fixed
Comment #5 on issue 140 by trond.norbye: "stats items" does not return
correct "age" value
http://code.google.com/p/memcached/issues/detail?id=140
The problem is that the stats items don't check if the oldest entry is
expired or not.
Hi Abhilash,
The Java client performs a size check on requests prior to making the
Memcache connection to stop excessive network usage if you accidentally try
to store more. You must configure the client to accept larger objects. You
may be able to do this in a config file, or it may require recom
On Nov 10, 4:21 pm, Abhilash wrote:
> I meant to run it with 5MB, so I have corrected it by changing it from
> 5120 to 5242880.
Ah, then use -I 5mb
> Even after running memcached with 5MB, I still get the error message -
> Caused by: java.lang.IllegalArgumentException: Cannot cache data
> lar
Thanks Trond, I changed the way I start memcached, as you suggested.
Can someone please respond to my last point?
>Even after running memcached with 5MB, I still get the error message -
>Caused by: java.lang.IllegalArgumentException: Cannot cache data
>larger than 1048576 bytes (1MB) (you tried t
Thanks Trond, I changed the way I start memcached, as you suggested.
Can someone please respond to my last point?
>Even after running memcached with 5MB, I still get the error message -
>Caused by: java.lang.IllegalArgumentException: Cannot cache data
>larger than 1048576 bytes (1MB) (you tried t
On 2. nov. 2010, at 10.36, nooby wrote:
> Hi,
>
> I got memcached 1.4.5 to compile however the following test failed:
>
> Assertion failed: response->message.header.response.status == status,
> file testapp.c, line 823
> *** Signal 6 - core dumped
> make: Fatal error: Command failed for target
Updates:
Status: Done
Comment #7 on issue 131 by trond.norbye: Outdated info in changelog?
http://code.google.com/p/memcached/issues/detail?id=131
(No comment was entered for this change.)
On 10. nov. 2010, at 16.21, Abhilash wrote:
> Hi Dustin, thanks for the quick response. Please see my comments
> below.
>
>> You've really gone out of your way to run it as root. Why is it so
>> important to you to do that? I think it's a rather awful idea.
>
> Can you please suggest the best
Hi Dustin, thanks for the quick response. Please see my comments
below.
>You've really gone out of your way to run it as root. Why is it so
>important to you to do that? I think it's a rather awful idea.
Can you please suggest the best way to run memcached, if running it as
root a bad idea.
Cor
Updates:
Status: Done
Comment #4 on issue 138 by trond.norbye: I can't install memcached on
HP-UNIX,can you help me?
http://code.google.com/p/memcached/issues/detail?id=138
Seems like you figured this one out. I'm closing the issue now that you've
got a workaround.
It would be nic
Updates:
Status: Fixed
Comment #7 on issue 111 by trond.norbye: compile errors: array subscript
has type 'char'
http://code.google.com/p/memcached/issues/detail?id=111
(No comment was entered for this change.)
Updates:
Status: Invalid
Comment #1 on issue 124 by trond.norbye: Please add Erlang memcached client
http://code.google.com/p/memcached/issues/detail?id=124
The link ( http://github.com/jacknyfe/mcd ) seeems to be dead
On Nov 10, 2:51 pm, Abhilash wrote:
> Memcached server version: memcached-1.4.5 on Linux 64Bit
> spy memcached client version: memcached-2.5
> sudo memcached -d -m 10240 -u root -I 5120 -u root -l [host] -p 11311
You've really gone out of your way to run it as root. Why is it so
important
Hi,
I have same problem, but starting memcached with -I is causing a
different issue. Can you please help?
Memcached server version: memcached-1.4.5 on Linux 64Bit
spy memcached client version: memcached-2.5
I have two Memcached Servers and they are started with following
command
sudo memcach
Updates:
Status: Fixed
Comment #2 on issue 155 by trond.norbye: able to tokenize and process
mulitple IP addresses when option -l is passed
http://code.google.com/p/memcached/issues/detail?id=155
Fixed in c605b31f2323aa0b81af65ce0bfbe0da249cb08b
Comment #2 on issue 161 by zhuizhuhaomeng: cache_create fatal error
http://code.google.com/p/memcached/issues/detail?id=161
So happy that I find a bug.
Comment #4 on issue 162 by ferranbonas: Starting memcached from cron or
sudo eats 1.5GB Virtual Memory
http://code.google.com/p/memcached/issues/detail?id=162
And the one with the 80Mb:
22184: memcached -d -p 11211 -u memcached -m 2048 -c 65535 -P
/var/run/memcached/memcached.pid -l 10.1
Comment #3 on issue 162 by ferranbonas: Starting memcached from cron or
sudo eats 1.5GB Virtual Memory
http://code.google.com/p/memcached/issues/detail?id=162
Here isthe pmap of the daemon with high virtual mem usage:
16977: memcached -d -p 11211 -u memcached -m 2048 -c 65535 -P
/var/run
Comment #2 on issue 162 by ferranbonas: Starting memcached from cron or
sudo eats 1.5GB Virtual Memory
http://code.google.com/p/memcached/issues/detail?id=162
[r...@em-lam-front-01 ~]# memcached -d -p 11211 -u memcached -m 2048 -c
65535 -P /var/run/memcached/memcached.pid -l 10.13.0.120
[
Updates:
Status: Fixed
Comment #1 on issue 161 by trond.norbye: cache_create fatal error
http://code.google.com/p/memcached/issues/detail?id=161
You're right. Seems that the cache wouldn't work if you tried to use a
cache setup with less than a pointer size... luckily for us we never
Comment #1 on issue 162 by trond.norbye: Starting memcached from cron or
sudo eats 1.5GB Virtual Memory
http://code.google.com/p/memcached/issues/detail?id=162
I tried to reproduce this on Solaris, but I failed..
from ./memcached:
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU P
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 162 by ferranbonas: Starting memcached from cron or sudo eats
1.5GB Virtual Memory
http://code.google.com/p/memcached/issues/detail?id=162
What steps will reproduce the problem?
1.Start memcached using "sudo memcached" or
26 matches
Mail list logo
