Bug #20646 Node corruption after REDO logs overloaded eror
Submitted: 23 Jun 2006 3:04 Modified: 23 Jul 2006 6:28
Reporter: Lachlan Mulcahy Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.0.21 cluster OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[23 Jun 2006 3:04] Lachlan Mulcahy 
Description:
After receiving a "Got temporary error 410 'REDO log files overloaded, consult online manual" error, nodes were corrupted:

Node 3: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 0. Caused by error 2815: 'File not found(Ndbd file system inconsistency error, please report a bug). Ndbd file system error, restart node initial'.
Node 2: Forced node shutdown completed. Occured during startphase 4. Initiated by signal 0. Caused by error 2815: 'File not found(Ndbd file system inconsistency error, please report a bug). Ndbd file system error, restart node initial'.

How to repeat:
Possibly increase TimeBetweenLocalCheckpoints and/or decrease NoOfFragmentLogFiles until your transaction load overloads the REDO logs.

Suggested fix:
n/a
[23 Jun 2006 5:38] Stewart Smith 
would be good to get the logs from the cluster.

this can be fetched with (i think it's included in that release) ndb_error_reporter or by manually copying ndb_*log and ndb*trace*
[23 Jun 2006 6:28] Jonas Oreland 
Did they change the value on "NoOfFragmentLogfiles". if they did, then this is not a bug.

After changing that value, you need to perform a rolling restart --initial
A system restart will not work.

But they should be able to change it back, perfrom a system restart.
And the change it using rolling restart --initial
[23 Jul 2006 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".