Author: tbedford
Date: 2009-03-04 10:33:17 +0100 (Wed, 04 Mar 2009)
New Revision: 14067
Log:
Added entry for bug #43239
Modified:
trunk/dynamic-docs/changelog/monitor.xml
Modified: trunk/dynamic-docs/changelog/monitor.xml
===================================================================
--- trunk/dynamic-docs/changelog/monitor.xml 2009-03-04 09:32:57 UTC (rev 14066)
+++ trunk/dynamic-docs/changelog/monitor.xml 2009-03-04 09:33:17 UTC (rev 14067)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1224 bytes
@@ -9,6 +9,38 @@
<logentry entrytype="bug">
<bugs>
+ <fixes bugid="43239"/>
+ </bugs>
+
+ <versions>
+ <version ver="2.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When a data collection became invalid, the agent sent NULLs for
+ those collection values. However, the timestamps that it sent
+ with the values were the timestamps from the last valid value
+ that was collected.
+ </para>
+
+ <para>
+ Due to key constraints on the Service Manager side, MySQL
+ Enterprise Monitor disregarded anything sent with duplicate
+ timestamps, thus the NULLs received from the agent were never
+ processed. Some mechanisms, such as replication discovery,
+ depend on the NULLs to identify a situation where data has
+ become invalid.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
<fixes bugid="43240"/>
</bugs>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r14067 - trunk/dynamic-docs/changelog | anthony.bedford | 4 Mar |
