Earlier this year

• Jun 22, 2009

  r17 (import bugfix from issue 3 ) committed by shellcode   -   import bugfix from issue 3

  import bugfix from issue 3
• Jun 22, 2009

  issue 3 (For some keys ketama_hashi returns 0) Status changed by shellcode   -   patch applied to trunk

  Status: Fixed

  patch applied to trunk

  Status: Fixed
• May 01, 2009

  issue 3 (For some keys ketama_hashi returns 0) commented on by mohanjith   -   I forgot to mention, I'm using memagent trunk.

  I forgot to mention, I'm using memagent trunk.
• May 01, 2009

  issue 3 (For some keys ketama_hashi returns 0) reported by mohanjith   -   What steps will reproduce the problem? 1. ketama.c:ketama_hashi returns 0 for some keys e.g. wp_:posts:84 2. This makes magent to crash if using ketama (in ketama.c:get_server) What is the expected output? What do you see instead? magent crashing from time to time with a segfault, when using ketama. This makes it impossible to use magent with ketama. What version of the product are you using? On what operating system? - Linux 2.6.28-11 - libevent 1.3 - gcc 4.3.3 Please provide any additional information below. I do not quite understand what ketama_hashi does and whether 0 is a valid value. But as a work around I'm not searching for the server in ketama.c:get_server (aprox line 431). Instead of while (1), I'm doing while (h) . I have attached my patch, but please use it at your own risk

  What steps will reproduce the problem? 1. ketama.c:ketama_hashi returns 0 for some keys e.g. wp_:posts:84 2. This makes magent to crash if using ketama (in ketama.c:get_server) What is the expected output? What do you see instead? magent crashing from time to time with a segfault, when using ketama. This makes it impossible to use magent with ketama. What version of the product are you using? On what operating system? - Linux 2.6.28-11 - libevent 1.3 - gcc 4.3.3 Please provide any additional information below. I do not quite understand what ketama_hashi does and whether 0 is a valid value. But as a work around I'm not searching for the server in ketama.c:get_server (aprox line 431). Instead of while (1), I'm doing while (h) . I have attached my patch, but please use it at your own risk

Older

• Nov 30, 2008

  r16 (remove assert()) committed by shellcode   -   remove assert()

  remove assert()
• Oct 04, 2008

  issue 2 (Missed headers) commented on by shellcode   -   fix header file include under BSD systems in svn repos

  fix header file include under BSD systems in svn repos
• Oct 04, 2008

  r15 (fix header file include under BSD systems) committed by shellcode   -   fix header file include under BSD systems

  fix header file include under BSD systems
• Sep 27, 2008

  r14 (add -lm to Makefile) committed by shellcode   -   add -lm to Makefile

  add -lm to Makefile
• Sep 27, 2008

  r13 (rewrite code of handle backup server) committed by shellcode   -   rewrite code of handle backup server

  rewrite code of handle backup server
• Sep 26, 2008

  issue 2 (Missed headers) reported by 191919   -   (1) ~/box/magent# make gcc -Wall -O2 -g -c -o magent.o magent.c magent.c: In function 'writev_list': magent.c:592: error: 'SSIZE_MAX' undeclared (first use in this function) <limits.h> should be #include'd. (2) ~/box/magent# make gcc -Wall -O2 -g -c -o magent.o magent.c magent.c: In function 'writev_list': magent.c:606: warning: implicit declaration of function 'writev' <sys/uio.h> should be #include'd.

  (1) ~/box/magent# make gcc -Wall -O2 -g -c -o magent.o magent.c magent.c: In function 'writev_list': magent.c:592: error: 'SSIZE_MAX' undeclared (first use in this function) <limits.h> should be #include'd. (2) ~/box/magent# make gcc -Wall -O2 -g -c -o magent.o magent.c magent.c: In function 'writev_list': magent.c:606: warning: implicit declaration of function 'writev' <sys/uio.h> should be #include'd.
• Sep 23, 2008

  r12 (code cleanup) committed by shellcode   -   code cleanup

  code cleanup
• Sep 23, 2008

  r11 (combine drive_get_server with drive_server functions to driv...) committed by shellcode   -   combine drive_get_server with drive_server functions to drive_memcached_server

  combine drive_get_server with drive_server functions to drive_memcached_server
• Sep 22, 2008

  r10 (put "END\r\n" in the last packet of GET/GETS response) committed by shellcode   -   put "END\r\n" in the last packet of GET/GETS response

  put "END\r\n" in the last packet of GET/GETS response
• Sep 19, 2008

  r9 (support unix domain socket) committed by shellcode   -   support unix domain socket

  support unix domain socket
• Sep 14, 2008

  r8 (supports backup server) committed by shellcode   -   supports backup server

  supports backup server
• Sep 12, 2008

  HowMagentWorks Wiki page edited by shellcode
• Sep 12, 2008

  HowMagentWorks Wiki page edited by shellcode
• Sep 12, 2008

  HowMagentWorks Wiki page added by shellcode
• Sep 10, 2008

  r4 (ketama allocation algorithm added) committed by shellcode   -   ketama allocation algorithm added

  ketama allocation algorithm added
• Sep 10, 2008

  r3 (handle more than 7 keys of get/gets command) committed by shellcode   -   handle more than 7 keys of get/gets command

  handle more than 7 keys of get/gets command
• Sep 07, 2008

  issue 1 (Purpose of memagent) commented on by shellcode   -   yeah. you r right! so php can connect local magent, instead of a lot of memcached servers.

  yeah. you r right! so php can connect local magent, instead of a lot of memcached servers.
• Sep 07, 2008

  issue 1 (Purpose of memagent) commented on by 191919   -   What you meant by 'memcached server farms', is it a group of memcached servers and each of them stores a subset, just like the memcache php extension?

  What you meant by 'memcached server farms', is it a group of memcached servers and each of them stores a subset, just like the memcache php extension?
• Sep 07, 2008

  issue 1 (Purpose of memagent) commented on by shellcode   -   one more comment: we can add one management port for magent which provides some handy tools such as to enable/disable backend on the fly

  one more comment: we can add one management port for magent which provides some handy tools such as to enable/disable backend on the fly
• Sep 07, 2008

  issue 1 (Purpose of memagent) commented on by shellcode   -   1) magent will write one key-value pair to normal memcached server farms and backup server farms at the same time. it's in TODO list 2) currently max free keep-alive connection number to one backend is 50(hard coded by #define MAXIDEL 50). it can be configured by arugment if needed 3) health check is in TODO list.

  1) magent will write one key-value pair to normal memcached server farms and backup server farms at the same time. it's in TODO list 2) currently max free keep-alive connection number to one backend is 50(hard coded by #define MAXIDEL 50). it can be configured by arugment if needed 3) health check is in TODO list.
• Sep 07, 2008

  issue 1 (Purpose of memagent) reported by 191919   -   Not really an issue, but some questions: 1. Does magent duplicates a key-value pair to multiple memcached backends, or just one of them? 2. How many connections magent will establish to *one* backend? 3. Is there a way to know whether a backend is live or dead, and how to manually mark a backend as live or dead? Thanks a lot, it's a good idea. :)

  Not really an issue, but some questions: 1. Does magent duplicates a key-value pair to multiple memcached backends, or just one of them? 2. How many connections magent will establish to *one* backend? 3. Is there a way to know whether a backend is live or dead, and how to manually mark a backend as live or dead? Thanks a lot, it's a good idea. :)
• Sep 07, 2008

  r2 (initial working release, version 0.2) committed by shellcode   -   initial working release, version 0.2

  initial working release, version 0.2
• Sep 04, 2008

  Project memagent created by shellcode   -   simple but useful proxy program for memcached server

  simple but useful proxy program for memcached server