Bug #18298 8 Node restart with table/index wo/ logging cause crash
Submitted: 17 Mar 2006 9:09 Modified: 27 Mar 2006 13:37
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1,5.0,5.1 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[17 Mar 2006 9:09] Jonas Oreland
Create table with ordered index
  (or table/unique index wo/ logging)

make 8 repeated node restart.

the problem is that this will create a new crashed replica even if table is not LCP:ed
and since it's not LCP, these wont be cleared

How to repeat:
see descr.

Suggested fix:
don't create crashed replica for table wo/ logging
[17 Mar 2006 9:11] 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:

[24 Mar 2006 12:31] Jonas Oreland
pushed into 5.1.8
[27 Mar 2006 10:13] Jonas Oreland
pushed into 5.0.20
[27 Mar 2006 12:05] Jonas Oreland
pushed into 4.1.19
[27 Mar 2006 13:37] Jon Stephens
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.

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

Additional info:

Documented bugfix in 4.1.19, 5.0.20, and 5.1.8 changelogs. Closed.