Bug #50370 Include nodeid in cluster log for management node messages
Submitted: 15 Jan 2010 14:42 Modified: 19 Jan 2010 14:08
Reporter: Geert Vanderkelen Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-ndb-7.0 OS:Any
Assigned to: Magnus Blåudd CPU Architecture:Any

[15 Jan 2010 14:42] Geert Vanderkelen
Description:
Never thought of it before, but the cluster logs don't show the node id for entries coming from the management node themselves:

2010-01-12 11:34:44 [MgmSrvr] INFO     -- NDB Cluster Management Server. mysql-5.1.37 ndb-6.3.27a-GA
2010-01-12 11:34:44 [MgmSrvr] INFO     -- Id: 1, Command port: *:1186

'Id: 1' is the management node, but why not 'Node 1:' instead?

How to repeat:
Check cluster logs.

Suggested fix:
Add 'Node <id>:' also to the log entries from the management node, so it's consistent with the other entries?
[18 Jan 2010 8:15] Bernd Ocklin
When changing these things which seem minor: we should always be aware that it might break someone's scripts.
[18 Jan 2010 17:32] Magnus Blåudd
you can already do ./ndb_mgmd --logname=<any text>, maybe that is enough?
[19 Jan 2010 14:08] Jørgen Austvik
Won't fix because of backwards compatibility