List:Commits« Previous MessageNext Message »
From:jon Date:February 13 2007 5:39am
Subject:svn commit - mysqldoc@docsrva: r4918 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2007-02-13 05:39:06 +0100 (Tue, 13 Feb 2007)
New Revision: 4918

Log:

Shared/network filesystems not recommended or supported for Cluster.



Modified:
   branches/telcos/refman-5.1/faqs.xml
   branches/telcos/refman-5.1/mysql-cluster.xml
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-5.0/faqs.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.1/faqs.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: branches/telcos/refman-5.1/faqs.xml
===================================================================
--- branches/telcos/refman-5.1/faqs.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ branches/telcos/refman-5.1/faqs.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 1, Lines Added: 40, Lines Deleted: 0; 2072 bytes

@@ -3635,6 +3635,46 @@
         </answer>
 
       </qandaentry>
+      
+      <qandaentry>
+        <question>
+          <para>
+            What filesystems can I use with MySQL Cluster? What about
+            network filesystems or network shares?
+          </para>
+        </question>
+        
+        <answer>
+          <para>
+            Generally, any filesystem that is native to the host
+            operating system should work well with MySQL Cluster. If you
+            find that a given filesystem works particularly well (or
+            not so especially well) with MySQL Cluster, we invite you to
+            discuss your findings in the 
+            <ulink url="&base-url-forum-list;?25">MySQL Cluster
+              Forums</ulink>.
+          </para>
+          
+          <para>
+            We do not test MySQL Cluster with <literal>FAT</literal>
+            or <literal>VFAT</literal> filesystems on Linux. Because of
+            this, and due to the fact that these are not very useful for
+            any purpose other than sharing disk partitions between Linux
+            and Windows operating systems on multi-boot computers, we
+            do not recommend their use with MySQL Cluster.
+          </para>
+          
+          <para>
+            MySQL Cluster is implemented as a shared-nothing solution;
+            the idea behind this is that the failure of a single piece
+            of hardware should not cause the failure of multiple cluster
+            nodes, or possibly even the failure of the cluster as a
+            whole. For this reason, the use of network shares or network
+            filesystems is not supported for MySQL Cluster. This also
+            applies to shared storage devices such as SANs.
+          </para>
+        </answer>
+      </qandaentry>
 
       <qandaentry>
 


Modified: branches/telcos/refman-5.1/mysql-cluster.xml
===================================================================
--- branches/telcos/refman-5.1/mysql-cluster.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ branches/telcos/refman-5.1/mysql-cluster.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 5; 1827 bytes

@@ -217,15 +217,22 @@
       <primary>MySQL Cluster</primary>
       <secondary>general description</secondary>
     </indexterm>
-
+    
     <para>
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
       clustering of in-memory databases in a shared-nothing system. The
       shared-nothing architecture allows the system to work with very
-      inexpensive hardware, and without any specific requirements on
-      hardware or software. It also does not have any single point of
-      failure because each component has its own memory and disk.
+      inexpensive hardware, and with a minimum of specific requirements
+      for hardware or software.
     </para>
+    
+    <para>
+      MySQL Cluster is designed not to have any single point of
+      failure. For this reason, each component is expected to have its
+      own memory and disk, and the use of shared storage mechanisms such
+      as network shares, network filesystems, and SANs is not
+      recommended or supported.
+    </para>
 
     <para>
       MySQL Cluster integrates the standard MySQL server with an

@@ -381,7 +388,7 @@
       <emphasis role="bold">Note</emphasis>: In many contexts, the term
       <quote>node</quote> is used to indicate a computer, but when
       discussing MySQL Cluster it means a <emphasis>process</emphasis>.
-      It is posible to run any number of nodes on a single computer, for
+      It is possible to run any number of nodes on a single computer, for
       which we use the term <firstterm>cluster host</firstterm>.
     </para>
 


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ trunk/refman-4.1/mysql-cluster.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 5; 1797 bytes

@@ -218,15 +218,22 @@
       <primary>MySQL Cluster</primary>
       <secondary>general description</secondary>
     </indexterm>
-
+    
     <para>
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
       clustering of in-memory databases in a shared-nothing system. The
       shared-nothing architecture allows the system to work with very
-      inexpensive hardware, and without any specific requirements on
-      hardware or software. It also does not have any single point of
-      failure because each component has its own memory and disk.
+      inexpensive hardware, and with a minimum of specific requirements
+      for hardware or software.
     </para>
+    
+    <para>
+      MySQL Cluster is designed not to have any single point of
+      failure. For this reason, each component is expected to have its
+      own memory and disk, and the use of shared storage mechanisms such
+      as network shares, network filesystems, and SANs is not
+      recommended or supported.
+    </para>
 
     <para>
       MySQL Cluster integrates the standard MySQL server with an

@@ -382,7 +389,7 @@
       <emphasis role="bold">Note</emphasis>: In many contexts, the term
       <quote>node</quote> is used to indicate a computer, but when
       discussing MySQL Cluster it means a <emphasis>process</emphasis>.
-      It is posible to run any number of nodes on a single computer, for
+      It is possible to run any number of nodes on a single computer, for
       which we use the term <firstterm>cluster host</firstterm>.
     </para>
 


Modified: trunk/refman-5.0/faqs.xml
===================================================================
--- trunk/refman-5.0/faqs.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ trunk/refman-5.0/faqs.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 1, Lines Added: 42, Lines Deleted: 1; 2076 bytes

@@ -3643,8 +3643,49 @@
         </answer>
 
       </qandaentry>
-
+      
       <qandaentry>
+        <question>
+          <para>
+            What filesystems can I use with MySQL Cluster? What about
+            network filesystems or network shares?
+          </para>
+        </question>
+        
+        <answer>
+          <para>
+            Generally, any filesystem that is native to the host
+            operating system should work well with MySQL Cluster. If you
+            find that a given filesystem works particularly well (or
+            not so especially well) with MySQL Cluster, we invite you to
+            discuss your findings in the 
+            <ulink url="&base-url-forum-list;?25">MySQL Cluster
+              Forums</ulink>.
+          </para>
+          
+          <para>
+            We do not test MySQL Cluster with <literal>FAT</literal>
+            or <literal>VFAT</literal> filesystems on Linux. Because of
+            this, and due to the fact that these are not very useful for
+            any purpose other than sharing disk partitions between Linux
+            and Windows operating systems on multi-boot computers, we
+            do not recommend their use with MySQL Cluster.
+          </para>
+          
+          <para>
+            MySQL Cluster is implemented as a shared-nothing solution;
+            the idea behind this is that the failure of a single piece
+            of hardware should not cause the failure of multiple cluster
+            nodes, or possibly even the failure of the cluster as a
+            whole. For this reason, the use of network shares or network
+            filesystems is not supported for MySQL Cluster. This also
+            applies to shared storage devices such as SANs.
+          </para>
+        </answer>
+      </qandaentry>
+      
+      
+      <qandaentry>
 
         <question>
 


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ trunk/refman-5.0/mysql-cluster.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 4; 1675 bytes

@@ -223,10 +223,17 @@
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
       clustering of in-memory databases in a shared-nothing system. The
       shared-nothing architecture allows the system to work with very
-      inexpensive hardware, and without any specific requirements on
-      hardware or software. It also does not have any single point of
-      failure because each component has its own memory and disk.
+      inexpensive hardware, and with a minimum of specific requirements
+      for hardware or software.
     </para>
+    
+    <para>
+      MySQL Cluster is designed not to have any single point of
+      failure. For this reason, each component is expected to have its
+      own memory and disk, and the use of shared storage mechanisms such
+      as network shares, network filesystems, and SANs is not
+      recommended or supported.
+    </para>
 
     <para>
       MySQL Cluster integrates the standard MySQL server with an

@@ -382,7 +389,7 @@
       <emphasis role="bold">Note</emphasis>: In many contexts, the term
       <quote>node</quote> is used to indicate a computer, but when
       discussing MySQL Cluster it means a <emphasis>process</emphasis>.
-      It is posible to run any number of nodes on a single computer, for
+      It is possible to run any number of nodes on a single computer, for
       which we use the term <firstterm>cluster host</firstterm>.
     </para>
 


Modified: trunk/refman-5.1/faqs.xml
===================================================================
--- trunk/refman-5.1/faqs.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ trunk/refman-5.1/faqs.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 1, Lines Added: 41, Lines Deleted: 1; 2069 bytes

@@ -3675,8 +3675,48 @@
         </answer>
 
       </qandaentry>
-
+      
+      
       <qandaentry>
+        <question>
+          <para>
+            What filesystems can I use with MySQL Cluster? What about
+            network filesystems or network shares?
+          </para>
+        </question>
+        
+        <answer>
+          <para>
+            Generally, any filesystem that is native to the host
+            operating system should work well with MySQL Cluster. If you
+            find that a given filesystem works particularly well (or
+            not so especially well) with MySQL Cluster, we invite you to
+            discuss your findings in the 
+            <ulink url="&base-url-forum-list;?25">MySQL Cluster
+              Forums</ulink>.
+          </para>
+          
+          <para>
+            We do not test MySQL Cluster with <literal>FAT</literal>
+            or <literal>VFAT</literal> filesystems on Linux. Because of
+            this, and due to the fact that these are not very useful for
+            any purpose other than sharing disk partitions between Linux
+            and Windows operating systems on multi-boot computers, we
+            do not recommend their use with MySQL Cluster.
+          </para>
+          
+          <para>
+            MySQL Cluster is implemented as a shared-nothing solution;
+            the idea behind this is that the failure of a single piece
+            of hardware should not cause the failure of multiple cluster
+            nodes, or possibly even the failure of the cluster as a
+            whole. For this reason, the use of network shares or network
+            filesystems is not supported for MySQL Cluster. This also
+            applies to shared storage devices such as SANs.
+          </para>
+        </answer>
+      </qandaentry>
+      <qandaentry>
 
         <question>
 


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2007-02-13 04:02:31 UTC (rev 4917)
+++ trunk/refman-5.1/mysql-cluster.xml	2007-02-13 04:39:06 UTC (rev 4918)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 4; 1342 bytes

@@ -218,15 +218,22 @@
       <primary>MySQL Cluster</primary>
       <secondary>general description</secondary>
     </indexterm>
-
+    
     <para>
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
       clustering of in-memory databases in a shared-nothing system. The
       shared-nothing architecture allows the system to work with very
-      inexpensive hardware, and without any specific requirements on
-      hardware or software. It also does not have any single point of
-      failure because each component has its own memory and disk.
+      inexpensive hardware, and with a minimum of specific requirements
+      for hardware or software.
     </para>
+    
+    <para>
+      MySQL Cluster is designed not to have any single point of
+      failure. For this reason, each component is expected to have its
+      own memory and disk, and the use of shared storage mechanisms such
+      as network shares, network filesystems, and SANs is not
+      recommended or supported.
+    </para>
 
     <para>
       MySQL Cluster integrates the standard MySQL server with an


Thread
svn commit - mysqldoc@docsrva: r4918 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1jon13 Feb