Bug #41505 [NdbApi] INFO & ERROR uses wrong date format in the MySQLD log
Submitted: 16 Dec 2008 13:55 Modified: 16 Dec 2008 13:56
Reporter: Jonathan Miller Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Linux
Assigned to: CPU Architecture:Any
Triage: Triaged: D4 (Minor) / R2 (Low) / E5 (Major)

[16 Dec 2008 13:55] Jonathan Miller
Description:
081216 11:29:26 [Note] NDB Binlog: logging ./insDel/account (UPDATED,USE_WRITE)
2008-12-16 10:09:54 [NdbApi] INFO     -- Flushing incomplete GCI:s < 126/12
2008-12-16 11:42:41 [NdbApi] ERROR    -- dropped GSN_SUB_TABLE_DATA due to wrong magic number
081216 14:12:00 [Note] NDB delete table: waiting max 119 sec for delete table ./insDel/account.  epochs: (7314/0,7314/0,7314/0)  injector proc_info: Waiting for event from ndbcluster

How to repeat:
N/A

Suggested fix:
use same date format as other messages in the log (081216)
[18 Dec 2008 10:22] Jonas Oreland
"unfortunately" the printouts come from very different parts of the code,
and aligning these would be a major effort

R2/E5

suggest to close as won't fix