MySQL Bugs: #82053: Failed to initialise m_max_warning

Bug #82053	Failed to initialise m_max_warning_level in thrman.cpp
Submitted:	29 Jun 2016 14:35	Modified:	8 Jul 2016 11:41
Reporter:	Mikael Ronström	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	7.5.3	OS:	Any
Assigned to:		CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
m_max_warning_level isn't initialised in thrman.cpp. So in some situations this can lead to crash in restart when it is "set" to 0.

How to repeat:
Run autotest suite, happens occasionally

Suggested fix:
Initialise m_max_warning_level

Documented fix in the NDB 7.5.4 changelog as follows:

    The internal variable m_max_warning_level was not initialized in
    thrman.cpp. This sometimes led to failures during a restart when the
    unitialized value was treated as 0.

Closed.