MySQL Bugs: #53876: ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER

Bug #53876	ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER
Submitted:	21 May 2010 8:59	Modified:	26 Jun 2010 9:32
Reporter:	Martin Zdila	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-5.1-telco-7.1	OS:	Linux (Debian Lenny)
Assigned to:		CPU Architecture:	Any
Tags:	7.1.3

Description:
original column type was varchar(255)

mysql> alter table pipeline_argument_to_entity_instance modify column name varchar(255) binary not null;
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER

How to repeat:
mysql> alter table pipeline_argument_to_entity_instance modify column name varchar(255) binary not null;
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER

[NDBD DEFAULT]
Datadir=/var/lib/mysql-cluster
NoOfReplicas=2
DataMemory=512M
IndexMemory=128M
MaxNoOfOrderedIndexes = 512
MaxNoOfUniqueHashIndexes = 256
MaxNoOfAttributes = 10000
MaxNoOfTables = 1000
FragmentLogFileSize = 64M

[NDB_MGMD DEFAULT]
Datadir=/var/lib/mysql-cluster

[NDB_MGMD]
Id=1
Hostname = majko

[NDB_MGMD]
Id=2
Hostname = matko

[NDBD]
Id=3
Hostname = alpha

[NDBD]
Id=4
Hostname = omega

[TCP DEFAULT]
SendBufferMemory = 20M
ReceiveBufferMemory = 20M

[API]
[API]
[API]
[API]

another issue seems to be related:

mysql> drop database gofer_martin;
ERROR 1051 (42S02): Unknown table 'organization,application_cache_bundle,mm_device_uaProfUrl,mm_device_tacs,build_platform_postprocessi'

also we could not dump the database anymore (some lock problem, errno: 157)

after cluster reastart the tables are gone (again).

157 is the error code for "could not connect to storage engine", so your cluster seems to be down ("ndb_mgm -e show" should tell whether that is the case) or the mysqld process can't connect to the cluster for some other reason.

The fact that the command line client reports "unknown error" instead of "could not connect to storage engine" has already been reported as bug #44817.

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".