Bug #60012 Change needed to Cluster 7.1.10 change history
Submitted: 8 Feb 2011 18:06 Modified: 10 Feb 2011 11:30
Reporter: Andrew Morgan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:Cluster 7.1.10 OS:Any
Assigned to: Jon Stephens CPU Architecture:Any

[8 Feb 2011 18:06] Andrew Morgan 
Description:
The change history at http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-news-5-1-51-ndb-7-1-10.html currently includes the statement "Setting this parameter to zero now disables the GCP monitor; this has the effect of disabling GCP stops" for "TimeBetweenEpochsTimeout".

Setting TimeBetweenEpochsTimeout does not prevent *all* GCP stops but prevents many GCP commit stops

How to repeat:
Read the documentation at http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-news-5-1-51-ndb-7-1-10.html

Suggested fix:
Replace phrase with "Setting this parameter to zero now disables the GCP monitor; this has the effect of preventing many GCP commit stops."
[8 Feb 2011 19:20] Jonas Oreland 
In fact, setting this value to 0, disables both GCP stop SAVE & COMMIT
So both types of GCP stop...
[10 Feb 2011 9:23] Jonas Oreland 
The current docs is a bit missleading in the "this has the effect of disabling GCP stops" for "TimeBetweenEpochsTimeout"."

There are 2 distinct types of GCP stop
1) Due to GCP_COMMIT taking too long,
   timeout for this is controlled by TimeBetweenEpochsTimeout
2) Due to GCP_SAVE taking too long
   this has a hard-coded timeout on 2 minutes

However, setting TimeBetweenEpochsTimeout=0 
disables *both* of these timeouts.
[10 Feb 2011 11:30] 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.

  Fixed BUG#58383 changelog entry

  Updated TimeBetweenEpochsTimeout, GCP stop description