Question to Cache::Memcached

[Garrett, Philip (MAN-Corporate)]

Joachim,

You probably need to upgrade Cache::Memcached.  The latest version (1.13)
fixes a network error-checking problem.

Philip

-----Original Message-----
From: memcached-admin@lists.danga.com
[mailto:memcached-admin@lists.danga.com]On Behalf Of Joachim
Bauernberger
Sent: Monday, June 07, 2004 7:57 AM
To: memcached@lists.danga.com
Subject: Question to Cache::Memcached


Hi,

not sure if this has been answered before, ..

I have just hooked up another box running memcached. The Frontendclient that

runs Cache::Memcached knows about both backend memcached instances but 
somehow only the first ip:port specified is used to store data.
The second box returns:

[misc][jmbdev]$ ./memcachestat.pl 10.0.33.122:11211
STAT pid 16686
STAT uptime 248863
STAT time 1086608492
STAT version 1.1.11
STAT rusage_user 0:730000
STAT rusage_system 1:300000
STAT curr_items 0
STAT total_items 0
STAT bytes 0
STAT curr_connections 81
STAT total_connections 82
STAT connection_structures 82
STAT cmd_get 0
STAT cmd_set 0
STAT get_hits 0
STAT get_misses 0
STAT bytes_read 31912
STAT bytes_written 1941274
STAT limit_maxbytes 536870912

Box #1:

[misc][jmbdev]$ ./memcachestat.pl 10.0.33.121:11211
STAT pid 18335
STAT uptime 938793
STAT time 1086608506
STAT version 1.1.11
STAT rusage_user 455:320000
STAT rusage_system 1762:30000
STAT curr_items 189580
STAT total_items 216524
STAT bytes 436967944
STAT curr_connections 81
STAT total_connections 306
STAT connection_structures 101
STAT cmd_get 1546868
STAT cmd_set 520589
STAT get_hits 933453
STAT get_misses 613415
STAT bytes_read 3443242023
STAT bytes_written 2403618753
STAT limit_maxbytes 1073741824

Does this have something to do with the "weight" parameter to new()?
   

Thanks,
~/joachim
-- 
Web: http://www.bauernberger.de