From 974b97a17538de1591ef2738975ce8aaa0e4b113 Mon Sep 17 00:00:00 2001 From: Philip Olson Date: Fri, 8 Feb 2013 07:09:45 +0000 Subject: [PATCH] A little cleanup git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@329449 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/mysqlnd_ms/quickstart.xml | 42 ++++++++++++++--------------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/reference/mysqlnd_ms/quickstart.xml b/reference/mysqlnd_ms/quickstart.xml index 43433b3b29..a338d673e6 100755 --- a/reference/mysqlnd_ms/quickstart.xml +++ b/reference/mysqlnd_ms/quickstart.xml @@ -1807,35 +1807,35 @@ if ($res) {
Partitioning and Sharding - Database clustering is done for various reasons. Cluster can improve availability, - fault tolerance but also to increase performance by applying a divide and conquer approach. - Work is distributed over many machines. Clustering is sometimes combined with - partitioning and sharding to further break up a big, complex task into - smaller, managable units. + Database clustering is done for various reasons. Clusters can improve availability, + fault tolerance, and increase performance by applying a divide and conquer approach + as work is distributed over many machines. Clustering is sometimes combined with + partitioning and sharding to further break up a large complex task into + smaller, more manageable units. - This plugin aims to support all kinds of MySQL database clusters. Some flavours of + The mysqlnd_ms plugin aims to support a wide variety of MySQL database clusters. Some flavors of MySQL database clusters have built-in methods for partitioning and sharding, - which may or may not be transparent to use. The plugin supports the two most - common approaches explicitly namely MySQL Replication table filtering and - application based partitioning or sharding. + which could be transparent to use. The plugin supports the two most + common approaches: MySQL Replication table filtering, and Sharding + (application based partitioning). - MySQL Replication supports partitioning in the form of filters that allow you to - create slaves replicating all database of the master or only certain databases - respectively tables. It is then in the responsibility of the application + MySQL Replication supports partitioning as filters that allow you to + create slaves that replicate all or specific databases of the master, or tables. + It is then in the responsibility of the application to choose a slave according to the filter rules. You can either use the - plugins node_groups filter to manually support this or use - the experimental table filter. + mysqlnd_ms node_groups filter to manually support this, + or use the experimental table filter. - Manual partitioning or sharding is supported through - node grouping filter and SQL hints since 1.5.0. The node_groups filter + Manual partitioning or sharding is supported through the + node grouping filter, and SQL hints as of 1.5.0. The node_groups filter lets you assign a symbolic name to a group of master and slave servers. In the example, the master master_0 and slave_0 form a group with the name Partition_A. It is entirely up to you to decide what makes up a group. For example, you may use node - groups for sharding and use the group name to address shards + groups for sharding, and use the group names to address shards like Shard_A_Range_0_100. @@ -1923,12 +1923,12 @@ select($mysqli, "slave_1", "/*Partition_A*/"); - By default the plugin will use all configured master and slave servers for - query execution. However, if a query begins with a SQL hint - /*node_group*/,the plugin will consider only the servers + By default, the plugin will use all configured master and slave servers for + query execution. But if a query begins with a SQL hint like + /*node_group*/, the plugin will only consider the servers listed in the node_group for query execution. Thus, SELECT queries prefixed with /*Partition_A*/ - are executed on slave_0 only. + will only be executed on slave_0.