MySQL中InnoDB的Memcached插件的使用教程_MySQL
安装
为了让文章更具完整性,我们选择从源代码安装MySQL,需要注意的是早期的版本有内存泄漏,所以推荐安装最新的稳定版,截至本文发稿时为止,最新的稳定版是5.6.13,我们就以此为例来说明,过程很简单,只要激活了WITH_INNODB_MEMCACHED即可:
shell> groupadd mysql shell> useradd -r -g mysql mysql shell> tar zxvf mysql-5.6.13.tar.gz shell> cd mysql-5.6.13 shell> cmake . -DWITH_INNODB_MEMCACHED=ON shell> make shell> make install shell> cd /usr/local/mysql shell> chown -R mysql . shell> chgrp -R mysql . shell> scripts/mysql_install_db --user=mysql shell> chown -R root . shell> chown -R mysql data shell> bin/mysqld_safe --user=mysql & shell> cp support-files/mysql.server /etc/init.d/mysql.server
MySQL安装完毕后,需要导入Memcached插件所需要的表结构:
mysql> SOURCE /usr/local/mysql/share/innodb_memcached_config.sql
一切就绪后就可以激活Memcached插件了(当然也可以禁止):
mysql> INSTALL PLUGIN daemon_memcached soname "libmemcached.so"; mysql> UNINSTALL PLUGIN daemon_memcached;
说明:以后一旦修改了原本已存在的Memcached插件的配置信息,均需要使用如上命令来重启Memcached插件(先uninstall,再install),以便让修改生效。
Memcached插件相关的配置信息如下,具体介绍可以参考官方文档:
mysql> SHOW VARIABLES LIKE '%memcached%'; +----------------------------------+------------------+ | Variable_name | Value | +----------------------------------+------------------+ | daemon_memcached_enable_binlog | OFF | | daemon_memcached_engine_lib_name | innodb_engine.so | | daemon_memcached_engine_lib_path | | | daemon_memcached_option | | | daemon_memcached_r_batch_size | 1 | | daemon_memcached_w_batch_size | 1 | +----------------------------------+------------------+
注意:daemon_memcached_r_batch_size和daemon_memcached_w_batch_size,这两个选项对性能影响较大,简单点说就是控制事务提交的频率,MySQL的缺省值均为1,也就是说每次都提交,这主要是从安全性考虑的,大家可以依照自己的情况来调整。
差不多了,此时Memcached端口应该准备就绪了,你可以试试看:
shell> echo "stats" | nc localhost 11211
换句话说,MySQL已经兼容Memcached协议,可以直接使用Memcached命令。
配置
在安装步骤里,我们导入了一个名为innodb_memcached_config.sql的脚本,它创建了一库(innodb_memcache)三表(cache_policies, config_options, containers):
mysql> USE innodb_memcache mysql> SHOW TABLES; +---------------------------+ | Tables_in_innodb_memcache | +---------------------------+ | cache_policies | | config_options | | containers | +---------------------------+
cache_policies定义了缓存策略,包含如下选择:
- innodb_only:只使用InnoDB作为数据存储。
- cache-only:只使用传统的Memcached引擎作为后端存储。
- caching:二者皆使用,如果在Memcached里找不到,就查询InnoDB。
config_options定义了分隔符号:
- separator:Memcached只识别单值,使用此分隔符(|)来连接多个字段的值。
- table_map_delimiter:通过此分隔符(.)来确认表和键,如:@@table.key。
如果我们想通过Memcached协议来访问一个表,需要先在containers中配置它:
代码如下:
mysql> SELECT * FROM containers\G
*************************** 1. row ***************************
name: aaa
db_schema: test
db_table: demo_test
key_columns: c1
value_columns: c2
flags: c3
cas_column: c4
expire_time_column: c5
unique_idx_name_on_key: PRIMARY
如上已经有了test数据库的demo_test表,通过c1查询c2的值,表结构如下所示:
mysql> DESC test.demo_test; +-------+---------------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------+---------------------+------+-----+---------+-------+ | c1 | varchar(32) | NO | PRI | | | | c2 | varchar(1024) | YES | | NULL | | | c3 | int(11) | YES | | NULL | | | c4 | bigint(20) unsigned | YES | | NULL | | | c5 | int(11) | YES | | NULL | | +-------+---------------------+------+-----+---------+-------+
缺省情况下有一行数据:
mysql> SELECT * FROM test.demo_test; +----+--------------+------+------+------+ | c1 | c2 | c3 | c4 | c5 | +----+--------------+------+------+------+ | AA | HELLO, HELLO | 8 | 0 | 0 | +----+--------------+------+------+------+
让我们用Memcached协议来访问看看:
shell> echo "get @@aaa.AA" | nc localhost 11211 VALUE @@aaa.AA 8 12 HELLO, HELLO END
我们还可以先设定缺省访问的表,然后后续的查询就只写键名就可以了:
shell> (echo "get @@aaa"; echo "get AA") | nc localhost 11211 VALUE @@aaa 0 14 test/demo_test END VALUE AA 8 12 HELLO, HELLO END
虽然我的例子都是通过命令行执行的,但是大家很容易就更改写成PHP之类的方法。
限制
Memcached插件用起来非常简单,不过并不是一切都很完美,比如说:当我们配置表的时候,containers表的字段,除了key_columns和value_columns以外,其它的字段,如:flags,cas_column,expire_time_column等也必须设定,可是很多时候,我们在原表中找不到贴切的字段,此时就只能对应新建三个字段,味道很恶心。
此外,containers表还有如下限制:
- key_columns字段的类型必须是CHAR或VARCHAR,且最大长度是250个字符。
- value_columns字段的类型必须是CHAR或VARCHAR或BLOB,长度不限。
- cas_column字段的类型必须是BIGINT。
- expiration_time_column字段的类型必须是INT。
- flags字段的类型必须是INT。
说明:随着MySQL版本的更新,这些限制可能会发生变化,请大家以实际情况为准。
实战
让我们以一个用户登录的例子来检验一下学习成果:
首先在测试数据库创建一个用户表:
USE `test` CREATE TABLE `users` ( `id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT, `username` VARCHAR(15) NOT NULL, `password` VARCHAR(32) NOT NULL, `email` text NOT NULL, `flags` INT(10) UNSIGNED DEFAULT '0', `cas_column` BIGINT(20) UNSIGNED DEFAULT '0', `expire_time_column` INT(10) UNSIGNED DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `username` (`username`) ) ENGINE=InnoDB;
然后添加几行测试数据:
INSERT INTO `users` (`username`, `password`, `email`) VALUES ('foo', 'ffffffffffffffffffffffffffffffff', 'foo@domain.com'), ('bar', 'bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb', 'bar@domain.com'); 接着在containers里配置这个表: INSERT INTO innodb_memcache.containers ( name, db_schema, db_table, key_columns, value_columns, flags, cas_column, expire_time_column, unique_idx_name_on_key ) VALUES ( 'default', 'test', 'users', 'username', 'password|email', 'flags', 'cas_column', 'expire_time_column', 'username' );
这里我们定义了多个字段(password和email)作为value_columns,并且使用竖线作为分隔符,实际上使用空格,逗号之类分隔符也可以,在innodb_config.c文件的源代码中能查到如下关于分隔符的定义,文档里并没有涵盖这些信息:
static const char* sep = " ;,|\n";
最后使用Memcached协议来访问一下,这里我们换个花样,执行一个MGET操作:
shell> echo "get foo bar" | nc localhost 11211 VALUE foo 0 47 ffffffffffffffffffffffffffffffff|foo@domain.com VALUE bar 0 47 bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb|bar@domain.com END
既然我定义value_columns的时候设置了多个字段,那么返回数据的时候自然也返回多个字段的数据,并且它们依照innodb_memcache.config_options表中的separator字段来分隔,缺省情况下是一个竖线,如果你的字段内容里包含了竖线,那么就会和缺省值发生冲突,此时你可以更新separator的定义,比如改成三个竖线等等,需要提醒的是,修改后别忘了重启Memcached插件。
说明:因为们在配置的时候把表命名为default,所以在请求的时候不用传递表名。

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

You can open phpMyAdmin through the following steps: 1. Log in to the website control panel; 2. Find and click the phpMyAdmin icon; 3. Enter MySQL credentials; 4. Click "Login".

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

Redis uses a single threaded architecture to provide high performance, simplicity, and consistency. It utilizes I/O multiplexing, event loops, non-blocking I/O, and shared memory to improve concurrency, but with limitations of concurrency limitations, single point of failure, and unsuitable for write-intensive workloads.

MySQL and SQL are essential skills for developers. 1.MySQL is an open source relational database management system, and SQL is the standard language used to manage and operate databases. 2.MySQL supports multiple storage engines through efficient data storage and retrieval functions, and SQL completes complex data operations through simple statements. 3. Examples of usage include basic queries and advanced queries, such as filtering and sorting by condition. 4. Common errors include syntax errors and performance issues, which can be optimized by checking SQL statements and using EXPLAIN commands. 5. Performance optimization techniques include using indexes, avoiding full table scanning, optimizing JOIN operations and improving code readability.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

Effective monitoring of Redis databases is critical to maintaining optimal performance, identifying potential bottlenecks, and ensuring overall system reliability. Redis Exporter Service is a powerful utility designed to monitor Redis databases using Prometheus. This tutorial will guide you through the complete setup and configuration of Redis Exporter Service, ensuring you seamlessly build monitoring solutions. By studying this tutorial, you will achieve fully operational monitoring settings
