From: jon Date: February 1 2006 3:26am Subject: svn commit - mysqldoc@docsrva: r1162 - in trunk: refman-4.1 refman-5.0 refman-5.1 List-Archive: http://lists.mysql.com/commits/1978 Message-Id: <200602010326.k113QVM8026375@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2006-02-01 04:26:29 +0100 (Wed, 01 Feb 2006) New Revision: 1162 Log: Fixed some msic. issues in Cluster chapter. (Thanks, Paul!) Modified: trunk/refman-4.1/ndbcluster.xml trunk/refman-5.0/ndbcluster.xml trunk/refman-5.1/ndbcluster.xml Modified: trunk/refman-4.1/ndbcluster.xml =================================================================== --- trunk/refman-4.1/ndbcluster.xml 2006-02-01 02:02:30 UTC (rev 1161) +++ trunk/refman-4.1/ndbcluster.xml 2006-02-01 03:26:29 UTC (rev 1162) @@ -547,10 +547,12 @@ This section is a How-To that describes the basics for how to plan, install, configure, and run a MySQL Cluster. - Unlike the example in - , the result of - following the guidelines and procedures outlined here should be a - usable MySQL Cluster which meets minimum requirements for + Whereas the examples in + provide more + in-depth information on a variety of clustering options and + configuration, the result of following the guidelines and + procedures outlined here should be a usable MySQL Cluster which + meets the minimum requirements for availability and safeguarding of data. @@ -638,11 +640,11 @@ Each host in our scenario is an Intel-based desktop PC running a common, generic Linux distribution installed to disk in a standard configuration, and running no unnecessary services. - The core OS with a standard TCP/IP networking client should be - sufficient. Also for the sake of simplicity, we also assume - that the filesystems on all hosts are set up identically. In - the event that they are not, you will need to adapt these - instructions accordingly. + The core OS with standard TCP/IP networking capabilities + should be sufficient. Also for the sake of simplicity, we also + assume that the filesystems on all hosts are set up + identically. In the event that they are not, you will need to + adapt these instructions accordingly. @@ -1419,7 +1421,8 @@ that is to be part of the clustered database. The easiest way to accomplish this is to do a search-and-replace on the world.sql file and replace all - instances of TYPE=MyISAM with + instances of TYPE=MyISAM or + ENGINE=MyISAM with ENGINE=NDBCLUSTER. If you do not want to modify the file, you can also use ALTER TABLE to change their type. The particulars are @@ -7113,11 +7116,12 @@ - Event severity levels can be turned on or off. If a severity - level is turned on, all events with a priority less than or - equal to the category thresholds are logged. If the severity - level is turned off then no events belonging to that severity - level are logged. + Event severity levels can be turned on or off (using + CLUSTERLOG FILTER — see above). If a + severity level is turned on, then all events with a priority + less than or equal to the category thresholds are logged. If + the severity level is turned off then no events belonging to + that severity level are logged. @@ -9010,9 +9014,9 @@ There are several other optimized socket implementations for computer clusters, including Myrinet, Gigabit Ethernet, Infiniband and the VIA interface. We have tested MySQL Cluster - so far only with SCI sockets. We also include documentation - above on how to set up SCI sockets using ordinary TCP/IP for - MySQL Cluster. + so far only with SCI sockets. See + for information on how to set up SCI sockets using ordinary + TCP/IP for MySQL Cluster. @@ -9967,13 +9971,15 @@ - What storage engines does Cluster - support? + What storage engines are supported by MySQL Cluster? - NDB is the only MySQL storage engine that - supports clustering. + Clustering in MySQL is supported only by the + NDB storage engine. That is, in order for a + table to be shared between nodes in a cluster, it must be + created using ENGINE=NDB (or + ENGINE=NDBCLUSTER, which is equivalent). @@ -10338,10 +10344,11 @@ ¤t-series;, Cluster tables (that is, tables created with ENGINE=NDBCLUSTER) have only fixed-width rows. This means that (for example) each record containing a - VARCHAR(255) column will require 256 bytes - of storage for that column, regardless of the size of the data - stored therein. This issue is expected to be fixed in a future - MySQL release series. + VARCHAR(255) column will require space for + 255 characters (as required for the character set and + collation being used for the table), regardless of the actual + number of characters stored therein. This issue is expected to + be fixed in a future MySQL release series. @@ -10463,9 +10470,8 @@ Yes, so long as all machines and operating systems have the same endianness (all big-endian or all little-endian). It is also possible to use different MySQL Cluster releases on - different nodes (for example, 4.1.8 on some nodes and 4.1.9 on - others). However, we recommend this be done only as part of a - rolling upgrade procedure. + different nodes. However, we recommend this be done only as + part of a rolling upgrade procedure. @@ -10987,12 +10993,12 @@ As is usual in the context of a relational database, the term - table denotes an ordered set of identically - structured records. In MySQL Cluster, a database table is - stored in a data node as a set of fragments, each of which is - replicated on additional data nodes. The set of data nodes - replicating the same fragment or set of fragments is referred - to as a node group. + table denotes a set of identically structured + records. In MySQL Cluster, a database table is stored in a + data node as a set of fragments, each of which is replicated + on additional data nodes. The set of data nodes replicating + the same fragment or set of fragments is referred to as a + node group. Modified: trunk/refman-5.0/ndbcluster.xml =================================================================== --- trunk/refman-5.0/ndbcluster.xml 2006-02-01 02:02:30 UTC (rev 1161) +++ trunk/refman-5.0/ndbcluster.xml 2006-02-01 03:26:29 UTC (rev 1162) @@ -547,10 +547,12 @@ This section is a How-To that describes the basics for how to plan, install, configure, and run a MySQL Cluster. - Unlike the example in - , the result of - following the guidelines and procedures outlined here should be a - usable MySQL Cluster which meets minimum requirements for + Whereas the examples in + provide more + in-depth information on a variety of clustering options and + configuration, the result of following the guidelines and + procedures outlined here should be a usable MySQL Cluster which + meets the minimum requirements for availability and safeguarding of data. @@ -638,11 +640,11 @@ Each host in our scenario is an Intel-based desktop PC running a common, generic Linux distribution installed to disk in a standard configuration, and running no unnecessary services. - The core OS with a standard TCP/IP networking client should be - sufficient. Also for the sake of simplicity, we also assume - that the filesystems on all hosts are set up identically. In - the event that they are not, you will need to adapt these - instructions accordingly. + The core OS with standard TCP/IP networking capabilities + should be sufficient. Also for the sake of simplicity, we also + assume that the filesystems on all hosts are set up + identically. In the event that they are not, you will need to + adapt these instructions accordingly. @@ -7089,11 +7091,12 @@ - Event severity levels can be turned on or off. If a severity - level is turned on, all events with a priority less than or - equal to the category thresholds are logged. If the severity - level is turned off then no events belonging to that severity - level are logged. + Event severity levels can be turned on or off (using + CLUSTERLOG FILTER — see above). If a + severity level is turned on, then all events with a priority + less than or equal to the category thresholds are logged. If + the severity level is turned off then no events belonging to + that severity level are logged. @@ -8984,9 +8987,9 @@ There are several other optimized socket implementations for computer clusters, including Myrinet, Gigabit Ethernet, Infiniband and the VIA interface. We have tested MySQL Cluster - so far only with SCI sockets. We also include documentation - above on how to set up SCI sockets using ordinary TCP/IP for - MySQL Cluster. + so far only with SCI sockets. See + for information on how to set up SCI sockets using ordinary + TCP/IP for MySQL Cluster. @@ -9717,8 +9720,8 @@ MySQL replication: This will make it possible to update from any MySQL Server in the cluster and still have the MySQL Replication handled by one of the MySQL Servers in - the cluster and the installation on the slave side - consistent. + the cluster, with the state of the slave side remaining + consistent with the cluster acting as the master. @@ -9747,15 +9750,16 @@ User-defined partitioning: - Users will be able to define partitions based on the fields - part of the primary key. The MySQL Server will be able to - discover whether it is possible to prune away some of the - partitions from the WHERE clause. + Users will be able to define partitions based on columns + that are part of the primary key. The MySQL Server will be + able to discover whether it is possible to prune away some + of the partitions from the WHERE clause. Partitioning based on KEY, HASH, RANGE, and LIST handlers will be possible, as well as subpartitioning. This feature should also be available - for many other handlers. + for many other handlers, and not only NDB + Cluster. @@ -10247,13 +10251,15 @@ - What storage engines does Cluster - support? + What storage engines are supported by MySQL Cluster? - NDB is the only MySQL storage engine that - supports clustering. + Clustering in MySQL is supported only by the + NDB storage engine. That is, in order for a + table to be shared between nodes in a cluster, it must be + created using ENGINE=NDB (or + ENGINE=NDBCLUSTER, which is equivalent). @@ -10626,10 +10632,11 @@ (that is, tables created with ENGINE=NDBCLUSTER) have only fixed-width rows. This means that (for example) each record containing a - VARCHAR(255) column will require 256 bytes - of storage for that column, regardless of the size of the data - stored therein. This issue is expected to be fixed in a future - MySQL release series. + VARCHAR(255) column will require space for + 255 characters (as required for the character set and + collation being used for the table), regardless of the actual + number of characters stored therein. This issue is expected to + be fixed in a future MySQL release series. @@ -11274,12 +11281,12 @@ As is usual in the context of a relational database, the term - table denotes an ordered set of identically - structured records. In MySQL Cluster, a database table is - stored in a data node as a set of fragments, each of which is - replicated on additional data nodes. The set of data nodes - replicating the same fragment or set of fragments is referred - to as a node group. + table denotes a set of identically structured + records. In MySQL Cluster, a database table is stored in a + data node as a set of fragments, each of which is replicated + on additional data nodes. The set of data nodes replicating + the same fragment or set of fragments is referred to as a + node group. Modified: trunk/refman-5.1/ndbcluster.xml =================================================================== --- trunk/refman-5.1/ndbcluster.xml 2006-02-01 02:02:30 UTC (rev 1161) +++ trunk/refman-5.1/ndbcluster.xml 2006-02-01 03:26:29 UTC (rev 1162) @@ -547,10 +547,12 @@ This section is a How-To that describes the basics for how to plan, install, configure, and run a MySQL Cluster. - Unlike the example in - , the result of - following the guidelines and procedures outlined here should be a - usable MySQL Cluster which meets minimum requirements for + Whereas the examples in + provide more + in-depth information on a variety of clustering options and + configuration, the result of following the guidelines and + procedures outlined here should be a usable MySQL Cluster which + meets the minimum requirements for availability and safeguarding of data. @@ -638,11 +640,11 @@ Each host in our scenario is an Intel-based desktop PC running a common, generic Linux distribution installed to disk in a standard configuration, and running no unnecessary services. - The core OS with a standard TCP/IP networking client should be - sufficient. Also for the sake of simplicity, we also assume - that the filesystems on all hosts are set up identically. In - the event that they are not, you will need to adapt these - instructions accordingly. + The core OS with standard TCP/IP networking capabilities + should be sufficient. Also for the sake of simplicity, we also + assume that the filesystems on all hosts are set up + identically. In the event that they are not, you will need to + adapt these instructions accordingly. @@ -7087,11 +7089,12 @@ - Event severity levels can be turned on or off. If a severity - level is turned on, all events with a priority less than or - equal to the category thresholds are logged. If the severity - level is turned off then no events belonging to that severity - level are logged. + Event severity levels can be turned on or off (using + CLUSTERLOG FILTER — see above). If a + severity level is turned on, then all events with a priority + less than or equal to the category thresholds are logged. If + the severity level is turned off then no events belonging to + that severity level are logged. @@ -10638,9 +10641,9 @@ There are several other optimized socket implementations for computer clusters, including Myrinet, Gigabit Ethernet, Infiniband and the VIA interface. We have tested MySQL Cluster - so far only with SCI sockets. We also include documentation - above on how to set up SCI sockets using ordinary TCP/IP for - MySQL Cluster. + so far only with SCI sockets. See + for information on how to set up SCI sockets using ordinary + TCP/IP for MySQL Cluster. @@ -10683,16 +10686,15 @@ - [pd] I see no such list. Should we comment out the following - paragraph? + [js] Commented out the following paragraph until the 5.1 list is ready. - + @@ -11244,8 +11246,8 @@ &title-mysql-5-0-cluster-changes; - MySQL 5.0.3-beta and later releases contain a number of new - features that are likely to be of interest: + MySQL Cluster in versions 5.0.3-beta and later contains a number + of new features that are likely to be of interest: @@ -11375,8 +11377,8 @@ MySQL replication: This will make it possible to update from any MySQL Server in the cluster and still have the MySQL Replication handled by one of the MySQL Servers in - the cluster and the installation on the slave side - consistent. + the cluster, with the state of the slave side remaining + consistent with the cluster acting as the master. @@ -11405,15 +11407,16 @@ User-defined partitioning: - Users will be able to define partitions based on the fields - part of the primary key. The MySQL Server will be able to - discover whether it is possible to prune away some of the - partitions from the WHERE clause. + Users will be able to define partitions based on columns + that are part of the primary key. The MySQL Server will be + able to discover whether it is possible to prune away some + of the partitions from the WHERE clause. Partitioning based on KEY, HASH, RANGE, and LIST handlers will be possible, as well as subpartitioning. This feature should also be available - for many other handlers. + for many other handlers, and not only NDB + Cluster. @@ -11905,13 +11908,15 @@ - What storage engines does Cluster - support? + What storage engines are supported by MySQL Cluster? - NDB is the only MySQL storage engine that - supports clustering. + Clustering in MySQL is supported only by the + NDB storage engine. That is, in order for a + table to be shared between nodes in a cluster, it must be + created using ENGINE=NDB (or + ENGINE=NDBCLUSTER, which is equivalent). @@ -12284,10 +12289,11 @@ (that is, tables created with ENGINE=NDBCLUSTER) have only fixed-width rows. This means that (for example) each record containing a - VARCHAR(255) column will require 256 bytes - of storage for that column, regardless of the size of the data - stored therein. This issue is expected to be fixed in a future - MySQL release series. + VARCHAR(255) column will require space for + 255 characters (as required for the character set and + collation being used for the table), regardless of the actual + number of characters stored therein. This issue is expected to + be fixed in a future MySQL release series. @@ -12932,12 +12938,12 @@ As is usual in the context of a relational database, the term - table denotes an ordered set of identically - structured records. In MySQL Cluster, a database table is - stored in a data node as a set of fragments, each of which is - replicated on additional data nodes. The set of data nodes - replicating the same fragment or set of fragments is referred - to as a node group. + table denotes a set of identically structured + records. In MySQL Cluster, a database table is stored in a + data node as a set of fragments, each of which is replicated + on additional data nodes. The set of data nodes replicating + the same fragment or set of fragments is referred to as a + node group.