Author: jstephens
Date: 2005-12-06 12:42:12 +0100 (Tue, 06 Dec 2005)
New Revision: 495
Log:
The shared memory transporter for NDBCluster is experimental *only* and
is *not* officially supported in any MySQL release to date - users are
on their own in this regard unless they can find help in the forum or
mailing list. (Thanks, Tomas!)
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 2005-12-06 10:38:47 UTC (rev 494)
+++ trunk/refman-4.1/ndbcluster.xml 2005-12-06 11:42:12 UTC (rev 495)
@@ -4974,19 +4974,23 @@
use the shared memory transporter and configure it
automatically where possible, chiefly where more than one node
runs concurrently on the same cluster host. (In previous
- versions of MySQL Cluster, shared memory segments were
- supported only when the <literal>-max</literal> binary was
- built using <option>--with-ndb-shm</option>.) When explicitly
- defining shared memory as the connection method, it is
- necessary to define at least <literal>NodeId1</literal>,
+ versions of MySQL Cluster, shared memory segments functioned
+ only when the <literal>-max</literal> binary was built using
+ <option>--with-ndb-shm</option>.) When explicitly defining
+ shared memory as the connection method, it is necessary to
+ define at least <literal>NodeId1</literal>,
<literal>NodeId2</literal> and <literal>ShmKey</literal>. All
- other parameters have default values that will work out fine
- in most cases.
+ other parameters have default values that should work well in
+ most cases.
</para>
-
+
<para>
- <emphasis role="bold">Note</emphasis>: SHM support should
- still be considered experimental in MySQL 4.1.
+ <emphasis role="bold">Important</emphasis>: <emphasis>SHM
+ functionality is considered experimental only</emphasis>. It
+ is not officially supported in MySQL 4.1. This means that you must
+ determine for yourself or by using our free resources (forums,
+ mailing lists) whether it can be made to work correctly in
+ your specific case.
</para>
<itemizedlist>
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2005-12-06 10:38:47 UTC (rev 494)
+++ trunk/refman-5.0/ndbcluster.xml 2005-12-06 11:42:12 UTC (rev 495)
@@ -4986,23 +4986,24 @@
MySQL Cluster attempts to use the shared memory transporter
and configure it automatically where possible, chiefly where
more than one node runs concurrently on the same cluster host.
- (In early versions of MySQL Cluster, shared memory segments
- were supported only when the <literal>-max</literal> binary
- was built using <option>--with-ndb-shm</option>.) When
+ (In very early versions of MySQL Cluster, shared memory
+ segments functioned only when the <literal>-max</literal>
+ binary was built using <option>--with-ndb-shm</option>.) When
explicitly defining shared memory as the connection method, it
- is necessary to define at least <literal>NodeId1</literal>,
+ is necessary to define at least <literal>NodeId1</literal>,
<literal>NodeId2</literal> and <literal>ShmKey</literal>. All
- other parameters have default values that will work out fine
- in most cases.
+ other parameters have default values that should work well in
+ most cases.
</para>
- <remark role="todo">
- Determine if this still applies in 5.0. [js]
- </remark>
-
<para>
- <emphasis role="bold">Note</emphasis>: SHM support should
- still be considered experimental.
+ <emphasis role="bold">Important</emphasis>: <emphasis>SHM
+ functionality is considered experimental only</emphasis>. It
+ is not officially supported in any MySQL release series up to
+ and including ¤t-series;. This means that you must
+ determine for yourself or by using our free resources (forums,
+ mailing lists) whether it can be made to work correctly in
+ your specific case.
</para>
<itemizedlist>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2005-12-06 10:38:47 UTC (rev 494)
+++ trunk/refman-5.1/ndbcluster.xml 2005-12-06 11:42:12 UTC (rev 495)
@@ -4986,23 +4986,24 @@
MySQL Cluster attempts to use the shared memory transporter
and configure it automatically where possible, chiefly where
more than one node runs concurrently on the same cluster host.
- (In early versions of MySQL Cluster, shared memory segments
- were supported only when the <literal>-max</literal> binary
- was built using <option>--with-ndb-shm</option>.) When
+ (In very early versions of MySQL Cluster, shared memory
+ segments functioned only when the <literal>-max</literal>
+ binary was built using <option>--with-ndb-shm</option>.) When
explicitly defining shared memory as the connection method, it
- is necessary to define at least <literal>NodeId1</literal>,
+ is necessary to define at least <literal>NodeId1</literal>,
<literal>NodeId2</literal> and <literal>ShmKey</literal>. All
- other parameters have default values that will work out fine
- in most cases.
+ other parameters have default values that should work well in
+ most cases.
</para>
-
- <remark role="todo">
- Determine if this still applies in 5.0. [js]
- </remark>
-
+
<para>
- <emphasis role="bold">Note</emphasis>: SHM support should
- still be considered experimental.
+ <emphasis role="bold">Important</emphasis>: <emphasis>SHM
+ functionality is considered experimental only</emphasis>. It
+ is not officially supported in any MySQL release series up to
+ and including ¤t-series;. This means that you must
+ determine for yourself or by using our free resources (forums,
+ mailing lists) whether it can be made to work correctly in
+ your specific case.
</para>
<itemizedlist>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r495 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 6 Dec |
