MySQL Bugs: #74318: Incorrect check of node restart ongoing

Bug #74318	Incorrect check of node restart ongoing
Submitted:	10 Oct 2014 13:07	Modified:	22 Dec 2014 16:12
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.4.0	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Part of the new algorithm introduced in WL#7509 is to increase checkpoint speed when a node restart is
ongoing. The implementation of the check for this reports node restarts ongoing also when it isn't ongoing.

How to repeat:
Check printouts from ndbinfo table disk_write_speed_aggregate when running flexAsynch benchmark

Suggested fix:
When a node failure occurs then ensure that we checkpoint faster until the checkpoint is completed at least. Also checkpoint faster when we know that a node is restarting.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

  Documented fix in the NDB 7.4.3 changelog as follows:

    The check to determine when a node was restarting and so know
    when to apply accelerated local checkpoints sometimes reported a
    false positive.

  Closed.      

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html