Bug #33499 log levels are set on a per ndb_mgmd per subscriber basis.
Submitted: 24 Dec 2007 14:03 Modified: 9 Jan 2008 12:31
Reporter: Bogdan Kecman Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:all OS:Any
Assigned to: Jon Stephens CPU Architecture:Any
Tags: cluster, CLUSTERLOG, ndb_mgmd

[24 Dec 2007 14:03] Bogdan Kecman
log levels are set on a per ndb_mgmd per subscriber basis.

ndb_X_cluster.log writer is subscriber[0] of ndb_mgmd X. Setting log
level for any subscriber of a particular ndb_mgmd does not affect any
other subscriber nor does it affect anything in the other ndb_mgmd.

If a ndb_mgmd is restarted all log levels will be set to default for
this particular ndb_mgmd subscriber[0]. Other connected subscribers have
to reconnect to ndb_mgmd and will have to set their log levels again.

How to repeat:
start two management nodes
change log level on first management node
check log on second management node

Suggested fix:
eather explain this in documentation or change the behavior that log level on one mgm node affects other nodes - I suggest documentation change is better way to go
[9 Jan 2008 12:31] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.