Bug #25323 NDB binlog timer prints incorrect stats
| Submitted: | 29 Dec 2006 3:35 | Modified: | 7 Feb 2007 17:12 |
|---|---|---|---|
| Reporter: | Stewart Smith | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1.14 | OS: | |
| Assigned to: | Stewart Smith | CPU Architecture: | Any |
[1 Feb 2007 6:29]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/19160 ChangeSet@1.2417, 2007-02-01 17:28:41+11:00, stewart@willster.(none) +1 -0 BUG#25323 NDB binlog timer prints incorrect stats fix time period calculation
[1 Feb 2007 6:29]
Stewart Smith
pushed to 5.1-ndb
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: events are per wrong time period. How to repeat: enable RUN_NDB_BINLOG_TIMER Suggested fix: ===== sql/ha_ndbcluster_binlog.cc 1.90 vs edited ===== --- 1.90/sql/ha_ndbcluster_binlog.cc 2006-12-02 01:48:25 +11:00 +++ edited/sql/ha_ndbcluster_binlog.cc 2006-12-06 14:37:54 +11:00 @@ -3931,9 +3931,9 @@ "%ld(%d e/s), total time %ld(%d e/s)", (ulong)gci, event_count, write_timer.elapsed_ms(), - event_count / write_timer.elapsed_ms(), + (1000*event_count) / write_timer.elapsed_ms(), gci_timer.elapsed_ms(), - event_count / gci_timer.elapsed_ms()); + (1000*event_count) / gci_timer.elapsed_ms()); #endif } }