Author: jrussell
Date: 2011-01-27 23:34:51 +0100 (Thu, 27 Jan 2011)
New Revision: 24919
Log:
Edited changelog entry for several MEM bugs: 58829, 45509, 58977, 57957, 34186, 53017, 59105, 57809, 59103, 57303, 57059, 54356, 44005, 57593, 56734.
Modified:
trunk/dynamic-docs/changelog/monitor-1.xml
Modified: trunk/dynamic-docs/changelog/monitor-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/monitor-1.xml 2011-01-27 22:24:48 UTC (rev 24918)
+++ trunk/dynamic-docs/changelog/monitor-1.xml 2011-01-27 22:34:51 UTC (rev 24919)
Changed blocks: 2, Lines Added: 383, Lines Deleted: 1; 8122 bytes
@@ -8,7 +8,381 @@
<logentry entrytype="bug">
+ <tags>
+ <highlight type="innodb"/>
+ </tags>
+
<bugs>
+ <fixes bugid="45509"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.0"/>
+ </versions>
+
+ <message>
+
+ <para>
+ If the output from the <literal role="stmt">SHOW ENGINE INNODB
+ STATUS</literal> command is truncated because it exceeds the
+ size limit, and MySQL Enterprise Monitor cannot get information
+ about all InnoDB transactions, now a message is printed to the
+ agent log. To avoid the possibility of the status information
+ being truncated, enable the
+ <literal role="sysvar">innodb_status_file</literal> option.
+ MySQL Enterprise Monitor gets the status information from this
+ file if it is available. The status file is not subject to a
+ maximum size like the <literal role="stmt">SHOW ENGINE INNODB
+ STATUS</literal> output.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="58977"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.1"/>
+ <version ver="2.2.4"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Upgraded the bundled MySQL instance to 5.1.50.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="57957"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.2"/>
+ <version ver="2.2.4"/>
+ </versions>
+
+ <message>
+
+ <para>
+ For Solaris installations, MySQL Enterprise Monitor now uses the
+ 64-bit HotSpot JVM on platforms that support it. The
+ <literal>-d64</literal> flag is now included in the
+ <literal>JAVA_OPTS</literal> setting, in the
+ <literal>catalina.sh</literal> configuration file.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="58829"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.2"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Upgraded the bundled Java installation to version 6.0_22.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="34186"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.2"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The Manage Servers page now has a menu option <literal>[Enable |
+ disable] event blackout</literal>. You can set up blackout
+ periods through the Dashboard in addition to scripting them
+ through the REST API.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="53017"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.2.3"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When starting or stopping MySQL Enterprise Monitor services on
+ Windows systems, no error message was issued if the user account
+ did not have administrative privileges. Now, an error message is
+ shown in this case when starting or stopping the services from
+ the command line. When you use the Windows shortcut, you are
+ prompted for administrator credentials if necessary.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="59105"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.2"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The non-anonymous bind password fields could be incorrectly
+ greyed out when switching between <literal>Comparison</literal>
+ and <literal>Bind As User</literal> settings.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="57809"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.1"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The default MySQL port during MySQL Enterprise Monitor is now
+ 13306 if you select the bundled MySQL server, or 3306 if you
+ select an existing MySQL server instance.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="59103"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.2"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Each time LDAP settings were changed, the binding would fail
+ unless the non-anonymous bind user password was re-entered.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="57303"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.1"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The timestamp sent from the Aggregator to the Service Manager
+ reflected the time that a query was sent to the Aggregator, not
+ the time that the query was actually run. This could result in
+ inaccurate graphs if the query data was buffered before being
+ sent to the Aggregator.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="57059"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.1"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The agent update installer used default values instead of values
+ specified on the command line for <literal>--backupdir</literal>
+ and <literal>--restartImmediately</literal>, when the installer
+ was invoked in interactive (text / win32) mode.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="54356"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.2.4"/>
+ </versions>
+
+ <message>
+
+ <para>
+ HTML formatting for queries could fail with an exception.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="44005"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.1"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A new graph, <literal>InnoDB Transaction Lock Memory</literal>,
+ illustrates the number of undo log entries. This value is
+ derived from the Information_Schema column
+ <literal>INNODB_TRX.TRX_ROWS_MODIFIED</literal>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="57593"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.3.1"/>
+ </versions>
+
+ <message>
+
+ <para>
+ After upgrading the service manager, certain graphs were not
+ available and had to be re-imported.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags></tags>
+
+ <bugs>
+ <fixes bugid="56734"/>
+ </bugs>
+
+ <versions>
+ <version ver=""/>
+ </versions>
+
+ <message>
+
+ <para>
+ The User Search Pattern when defined in MEM/LDAP Bind as User
+ method of authentication overrides the User Search Attribute
+ Pattern method, even though it shows as greyed out.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
<fixes bugid="58391"/>
</bugs>
@@ -63,7 +437,15 @@
<message>
- <para></para>
+ <para>
+ When MySQL Enterprise Monitor truncated the the legacy data
+ collection tables, such as <literal>dc_ng_string_now</literal>
+ and <literal>dc_ng_long_now</literal>, the disk space was not
+ released back to the operating system, even if the
+ <literal role="sysvar">innodb_file_per_table</literal> setting
+ was enabled. Now, the disk space is released correctly, for all
+ combinations of MySQL with or without the InnoDB Plugin.
+ </para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r24919 - trunk/dynamic-docs/changelog | john.russell | 27 Jan |
