Author: mcbrown
Date: 2009-01-30 10:28:50 +0100 (Fri, 30 Jan 2009)
New Revision: 13452
Log:
Small update on the GRANTs needed during replication discovery
Modified:
trunk/mysql-monitor-2.0/install.xml
Modified: trunk/mysql-monitor-2.0/install.xml
===================================================================
--- trunk/mysql-monitor-2.0/install.xml 2009-01-30 09:21:54 UTC (rev 13451)
+++ trunk/mysql-monitor-2.0/install.xml 2009-01-30 09:28:50 UTC (rev 13452)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1718 bytes
@@ -1875,6 +1875,38 @@
</programlisting>
<para>
+ To enable replication discovery to work, you should also grant
+ the <literal>SELECT</literal> privilege on the
+ <literal>mysql.inventory</literal> table for each user with
+ replication privileges on the corresponding replication master.
+ This is required to let the &merlin_agent; read the replication
+ master UUID. For example:
+ </para>
+
+<programlisting>
+GRANT SELECT
+ ON mysql.inventory
+ TO '<replaceable>replicationuser</replaceable>'@'<replaceable>%</replaceable>'
+ IDENTIFIED BY '<replaceable>replication_password</replaceable>';
+</programlisting>
+
+ <para>
+ If the agent is unable to access the information from the table
+ then a warning containing this information will be written to
+ the agent log.
+ </para>
+
+ <note>
+ <para>
+ You may want to disable logging for the grant statement to
+ prevent the grant information being replicated to the slaves.
+ If this is the case, execute the statement <literal>SET
+ SQL_LOG_BIN=0</literal> before you execute the above
+ <literal>GRANT</literal> statement.
+ </para>
+ </note>
+
+ <para>
In a typical configuration, the agent runs on the same machine
as the MySQL server it is monitoring so the host name will be
<replaceable>localhost</replaceable>. However, this will change
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r13452 - trunk/mysql-monitor-2.0 | martin.brown | 30 Jan |
