MySQL Bugs: #33159: mysqld down when create mysql.ndb_replication with addition PRIMARY KEY

Bug #33159	mysqld down when create mysql.ndb_replication with addition PRIMARY KEY
Submitted:	12 Dec 2007 8:10	Modified:	7 Jan 2008 11:37
Reporter:	li zhou	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S1 (Critical)
Version:	5.1.22-ndb-6.3.6	OS:	Any
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
If we add additional column and primary key when creating mysql.ndb_replication table, mysqld will crash. 

How to repeat:
Create table as following statement:
binlog_type is not required column.

CREATE TABLE mysql.ndb_replication
  (db VARBINARY(63),
   table_name VARBINARY(63),
   server_id INT UNSIGNED,
   binlog_type INT UNSIGNED,
   db_type INT UNSIGNED,
   conflict_fn VARBINARY(128),
   PRIMARY KEY USING HASH (db,table_name,server_id,db_type))
  ENGINE=NDB PARTITION BY KEY(db,table_name,db_type);

Suggested fix:
Limited required columns.

Thank you for a bug report. If you got a crash, why do you think it is a feature request (S4)? I'd call it a serious bug (S1). Do you agree?

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/39890

ChangeSet@1.2789, 2007-12-13 14:30:18+01:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #33159  	mysqld down when create mysql.ndb_replication with addition PRIMARY KEY

fixed in 6.3.7

Documented bugfix in 5.1.23-ndb-6.3.7 changelog. Closed.