MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon Date:January 9 2008 12:29pm
Subject:svn commit - mysqldoc@docsrva: r9524 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: jstephens
Date: 2008-01-09 13:29:19 +0100 (Wed, 09 Jan 2008)
New Revision: 9524

Log:

Fixes Docs Bug #33499 (Thanks, BKecman!)



Modified:
   trunk/refman-4.1/mysql-cluster-management.xml
   trunk/refman-5.0/mysql-cluster-management.xml
   trunk/refman-5.1/mysql-cluster-management.xml
   trunk/refman-6.0/mysql-cluster-management.xml


Modified: trunk/refman-4.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-management.xml	2008-01-09 12:02:00 UTC (rev 9523)
+++ trunk/refman-4.1/mysql-cluster-management.xml	2008-01-09 12:29:19 UTC (rev 9524)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1206 bytes

@@ -1288,6 +1288,21 @@
         severity level are logged.
       </para>
 
+      <important>
+        <para>
+          Cluster log levels are set on a per
+          <command>ndb_mgmd</command>, per subscriber basis. This means
+          that, in a MySQL Cluster with multiple management servers,
+          using a <literal>CLUSTERLOG</literal> command in an instance
+          of <command>ndb_mgm</command> connected to one management
+          server affects only logs generated by that management server
+          but not by any of the others. This also means that, should one
+          of the management servers be restarted, only logs generated by
+          that management server are affected by the resetting of log
+          levels caused by the restart.
+        </para>
+      </important>
+
       <remark role="todo">
         Some further explanation of severity levels and an example would
         be good here.


Modified: trunk/refman-5.0/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster-management.xml	2008-01-09 12:02:00 UTC (rev 9523)
+++ trunk/refman-5.0/mysql-cluster-management.xml	2008-01-09 12:29:19 UTC (rev 9524)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1206 bytes

@@ -1324,6 +1324,21 @@
         severity level are logged.
       </para>
 
+      <important>
+        <para>
+          Cluster log levels are set on a per
+          <command>ndb_mgmd</command>, per subscriber basis. This means
+          that, in a MySQL Cluster with multiple management servers,
+          using a <literal>CLUSTERLOG</literal> command in an instance
+          of <command>ndb_mgm</command> connected to one management
+          server affects only logs generated by that management server
+          but not by any of the others. This also means that, should one
+          of the management servers be restarted, only logs generated by
+          that management server are affected by the resetting of log
+          levels caused by the restart.
+        </para>
+      </important>
+
       <remark role="todo">
         Some further explanation of severity levels and an example would
         be good here.


Modified: trunk/refman-5.1/mysql-cluster-management.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-management.xml	2008-01-09 12:02:00 UTC (rev 9523)
+++ trunk/refman-5.1/mysql-cluster-management.xml	2008-01-09 12:29:19 UTC (rev 9524)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1206 bytes

@@ -1363,6 +1363,21 @@
         severity level are logged.
       </para>
 
+      <important>
+        <para>
+          Cluster log levels are set on a per
+          <command>ndb_mgmd</command>, per subscriber basis. This means
+          that, in a MySQL Cluster with multiple management servers,
+          using a <literal>CLUSTERLOG</literal> command in an instance
+          of <command>ndb_mgm</command> connected to one management
+          server affects only logs generated by that management server
+          but not by any of the others. This also means that, should one
+          of the management servers be restarted, only logs generated by
+          that management server are affected by the resetting of log
+          levels caused by the restart.
+        </para>
+      </important>
+
       <remark role="todo">
         Some further explanation of severity levels and an example would
         be good here.


Modified: trunk/refman-6.0/mysql-cluster-management.xml
===================================================================
--- trunk/refman-6.0/mysql-cluster-management.xml	2008-01-09 12:02:00 UTC (rev 9523)
+++ trunk/refman-6.0/mysql-cluster-management.xml	2008-01-09 12:29:19 UTC (rev 9524)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1206 bytes

@@ -1353,6 +1353,21 @@
         severity level are logged.
       </para>
 
+      <important>
+        <para>
+          Cluster log levels are set on a per
+          <command>ndb_mgmd</command>, per subscriber basis. This means
+          that, in a MySQL Cluster with multiple management servers,
+          using a <literal>CLUSTERLOG</literal> command in an instance
+          of <command>ndb_mgm</command> connected to one management
+          server affects only logs generated by that management server
+          but not by any of the others. This also means that, should one
+          of the management servers be restarted, only logs generated by
+          that management server are affected by the resetting of log
+          levels caused by the restart.
+        </para>
+      </important>
+
       <remark role="todo">
         Some further explanation of severity levels and an example would
         be good here.


Thread
svn commit - mysqldoc@docsrva: r9524 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0jon9 Jan