Comments on: Installing memcached functions for MySQL http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql Blog by Shlomi Noach Wed, 01 Feb 2012 20:47:51 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Memcached Functions || libmemcached « Yref2's Blog http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-16349 Memcached Functions || libmemcached « Yref2's Blog Wed, 04 Aug 2010 10:12:10 +0000 http://code.openark.org/blog/?p=316#comment-16349 [...] Installing memcached functions for MySQL [...] [...] Installing memcached functions for MySQL [...]

]]> By: shlomi http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-15479 shlomi Mon, 05 Jul 2010 11:23:10 +0000 http://code.openark.org/blog/?p=316#comment-15479 @Martin, Joy of open source: a *lot* of compilations and complications. I'll be happy if you post another comments once you find the solution. Thanks @Martin,
Joy of open source: a *lot* of compilations and complications. I'll be happy if you post another comments once you find the solution.

Thanks

]]> By: Martin http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-15478 Martin Mon, 05 Jul 2010 10:54:38 +0000 http://code.openark.org/blog/?p=316#comment-15478 Thx for this great tutorial, I managed finally to compile and install everything on a debian lenny system. Just the last step doesn't work, when I try mysql -u root -p < sql/install_functions.sql mysql replies that the database is missing and when I add a --database=xxx the mysql replies 'ERROR 1126 (HY000) at line 1: Can't open shared library 'libmemcached_functions_mysql.so' (errno: 22 /usr/lib/mysql/libmemcached_functions_mysql.so: undefined symbol: memcached_string_append)' Maybe I will find a way, already checked the rights etc. Some day it will work :-) Thx for this great tutorial, I managed finally to compile and install everything on a debian lenny system.

Just the last step doesn't work, when I try

mysql -u root -p < sql/install_functions.sql

mysql replies that the database is missing and when I add a --database=xxx the mysql replies 'ERROR 1126 (HY000) at line 1: Can't open shared library 'libmemcached_functions_mysql.so' (errno: 22 /usr/lib/mysql/libmemcached_functions_mysql.so: undefined symbol: memcached_string_append)'

Maybe I will find a way, already checked the rights etc.

Some day it will work :-)

]]> By: Jo Yo http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-10516 Jo Yo Fri, 12 Feb 2010 20:47:18 +0000 http://code.openark.org/blog/?p=316#comment-10516 That's pretty slick. I like it. I made a UDF too that enables JavaScript to evaluate on MySQL. It could be helpful if you are into UDFs: http://bit.ly/cKA8np That's pretty slick. I like it. I made a UDF too that enables JavaScript to evaluate on MySQL. It could be helpful if you are into UDFs: http://bit.ly/cKA8np

]]> By: shlomi http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-5033 shlomi Tue, 20 Oct 2009 15:55:33 +0000 http://code.openark.org/blog/?p=316#comment-5033 @SailorCTO Hi, Thanks for posting. I'm unable at this moment to check this on my current setup, sorry :( Best if you could ping the appropriate forums, or even poke Patrick Galbraith :) Regards @SailorCTO

Hi,
Thanks for posting. I'm unable at this moment to check this on my current setup, sorry :(
Best if you could ping the appropriate forums, or even poke Patrick Galbraith :)

Regards

]]> By: SailorCTO http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-5030 SailorCTO Tue, 20 Oct 2009 14:11:24 +0000 http://code.openark.org/blog/?p=316#comment-5030 Nice post. I ran through all the install steps using YUM on my Fedora 10 machine and everything went smoothly, including the loading of UDFs. I can SELECT mem_setc('mykey', 'Some data here'); ...however...when I try to retrieve it with: SELECT mem_getc('mysql'); it finds the key, but null instead of 'Some data here'. Setup: Fedora 10 - kernel 2.6.27.37-170.2.104.fc10.i686 MySQL 5.0.84 Did I miss something? Nice post. I ran through all the install steps using YUM on my Fedora 10 machine and everything went smoothly, including the loading of UDFs.

I can
SELECT mem_setc('mykey', 'Some data here');

...however...when I try to retrieve it with:

SELECT mem_getc('mysql');

it finds the key, but null instead of 'Some data here'.

Setup:
Fedora 10 - kernel 2.6.27.37-170.2.104.fc10.i686
MySQL 5.0.84

Did I miss something?

]]> By: shlomi http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-1783 shlomi Sun, 03 May 2009 17:09:28 +0000 http://code.openark.org/blog/?p=316#comment-1783 @Pete Try running ldconfig --verbose to see the current search path. Either you put the libraries in one of the listed paths, or you create a sym link, or just add you path to /etc/ld.so.conf Shlomi @Pete
Try running
ldconfig --verbose
to see the current search path. Either you put the libraries in one of the listed paths, or you create a sym link, or just add you path to /etc/ld.so.conf

Shlomi

]]> By: Pete http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-1782 Pete Sun, 03 May 2009 16:29:25 +0000 http://code.openark.org/blog/?p=316#comment-1782 I am trying to install the memcache functions againt the packaged mysql-server but no matter what I do it always ends up saying it cannot load the library file when I try to install the functions in the database. I think I must have libdir wrong any ideas what the value should be? I am trying to install the memcache functions againt the packaged mysql-server but no matter what I do it always ends up saying it cannot load the library file when I try to install the functions in the database. I think I must have libdir wrong any ideas what the value should be?

]]> By: code.openark.org » Blog Archive » Using memcached functions for MySQL; an automated alternative to Query Cache http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-111 code.openark.org » Blog Archive » Using memcached functions for MySQL; an automated alternative to Query Cache Mon, 15 Dec 2008 05:56:18 +0000 http://code.openark.org/blog/?p=316#comment-111 [...] (See my previous post on how to install memcached functions for MySQL). [...] [...] (See my previous post on how to install memcached functions for MySQL). [...]

]]> By: Michael http://code.openark.org/blog/mysql/installing-memcached-functions-for-mysql/comment-page-1#comment-100 Michael Thu, 11 Dec 2008 18:00:55 +0000 http://code.openark.org/blog/?p=316#comment-100 I don't believe there are "best practices" per sé. memcached purposely decouples the hashing options and leaves the client responsible for choosing where to store and how to distribute the data. There are some "standards" in the sense that there are known libraries/implementations which have been adopted to be the leader in consistent hashing algorithms (e.g. ketama). However, ultimately its up to you on how to distribute and hash your keys. As an FYI, the whole "consistent distribution" issue came up when there was a large distributed memcached installation where if you had [initially] distributed your keys using a simple modulus algorithm, when/if you took one server out of the pool the entire cache would be invalidated as the modulus algorithm now returned different results. To address that, the consistent distribution concept came along so that in the event you add or remove memcached instances to your pool you will at worst invalidate cached objects on a single instance within the pool. This is because the consistent distribution algorithm says that key X is consistently assigned to server Y. When server Y is removed from the pool, the consistent hashing algorithm reassigns it to another server. When you add a server to the pool, key X will still [consistently] hash to server Y. I don't believe there are "best practices" per sé. memcached purposely decouples the hashing options and leaves the client responsible for choosing where to store and how to distribute the data. There are some "standards" in the sense that there are known libraries/implementations which have been adopted to be the leader in consistent hashing algorithms (e.g. ketama). However, ultimately its up to you on how to distribute and hash your keys.

As an FYI, the whole "consistent distribution" issue came up when there was a large distributed memcached installation where if you had [initially] distributed your keys using a simple modulus algorithm, when/if you took one server out of the pool the entire cache would be invalidated as the modulus algorithm now returned different results. To address that, the consistent distribution concept came along so that in the event you add or remove memcached instances to your pool you will at worst invalidate cached objects on a single instance within the pool. This is because the consistent distribution algorithm says that key X is consistently assigned to server Y. When server Y is removed from the pool, the consistent hashing algorithm reassigns it to another server. When you add a server to the pool, key X will still [consistently] hash to server Y.

]]>