Bug #20904 GCP Stop during GCP_SAVEREQ due to FILE_CHANGE_PROBLEM in zero-page

Submitted: 7 Jul 2006 14:00 Modified: 6 Sep 2006 10:33
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1,5.0,5.1 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[7 Jul 2006 14:00] Jonas Oreland 
Description:
During some situations with high disk-load, then writing of the redo-log
  could hang, causing crash with error message "GCP STOP detected"

How to repeat:
 

Suggested fix:
[7 Jul 2006 14:01] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/8910
[1 Sep 2006 8:09] Jonas Oreland 
pushed to 5.1.12
[1 Sep 2006 19:32] Jonas Oreland 
pushed to 5.0.25
[6 Sep 2006 7:09] Jonas Oreland 
pushed into 4.1.22
[6 Sep 2006 10:33] Jon Stephens 
Documented in 4.1.22, 5.0.25, and 5.1.12 changelogs.
[2 Apr 2007 11:41] Valeriy Kravchuk 
Bug #21984 was marked as a duplicate of this one.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.042 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.