NDB engine not available on mysqld note, even though enabled (8 replies)

We've done an initial test install of the cluster on a single server (all nodes, just for dev purposes).

In the my.cnf we are enabling the ndb engine

[mysqld]
ndbcluster
datadir=/home/mysqlc/mysqld_data
basedir=/home/mysqlc
port=5000

We start our config node, all OK:


MySQL Cluster Management Server mysql-5.5.19 ndb-7.2.4
2012-03-08 11:03:11 [ndbd] INFO -- Angel connected to 'localhost:1186'
2012-03-08 11:03:11 [ndbd] INFO -- Angel allocated nodeid: 3
2012-03-08 11:03:11 [ndbd] INFO -- Angel connected to 'localhost:1186'
2012-03-08 11:03:11 [ndbd] INFO -- Angel allocated nodeid: 4


We start our mysqld node, all seems OK too:


jacekf@jacekf64:/home/mysqlc/bin$ 120308 11:03:21 [Note] Plugin 'FEDERATED' is disabled.
120308 11:03:21 InnoDB: The InnoDB memory heap is disabled
120308 11:03:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120308 11:03:21 InnoDB: Compressed tables use zlib 1.2.3
120308 11:03:21 InnoDB: Using Linux native AIO
120308 11:03:21 InnoDB: Initializing buffer pool, size = 128.0M
120308 11:03:21 InnoDB: Completed initialization of buffer pool
120308 11:03:21 InnoDB: highest supported file format is Barracuda.
120308 11:03:22 InnoDB: Waiting for the background threads to start
120308 11:03:23 InnoDB: 1.1.8 started; log sequence number 1595685
120308 11:03:26 [Note] NDB: NodeID is 50, management server 'localhost:1186'
120308 11:03:26 [Note] NDB[0]: NodeID: 50, all storage nodes connected
120308 11:03:26 [Warning] NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by slave mysqlds
120308 11:03:26 [Note] Starting Cluster Binlog Thread
120308 11:03:27 [Note] Event Scheduler: Loaded 0 events
120308 11:03:27 [Note] /opt/mysql/server-5.5/bin/mysqld: ready for connections.
Version: '5.5.19-ndb-7.2.4-gpl' socket: '/tmp/mysql.sock' port: 5000 MySQL Cluster Community Server (GPL)
120308 11:03:28 [Note] NDB Binlog: DISCOVER TABLE Event: REPL$mysql/ndb_schema
120308 11:03:28 [Note] NDB Binlog: logging ./mysql/ndb_schema (UPDATED,USE_WRITE)
120308 11:03:28 [Note] NDB Binlog: DISCOVER TABLE Event: REPL$mysql/ndb_apply_status
120308 11:03:28 [Note] NDB Binlog: logging ./mysql/ndb_apply_status (UPDATED,USE_WRITE)
2012-03-08 11:03:28 [NdbApi] INFO -- Flushing incomplete GCI:s < 463973/0
2012-03-08 11:03:28 [NdbApi] INFO -- Flushing incomplete GCI:s < 463973/0
120308 11:03:28 [Note] NDB Binlog: starting log at epoch 463973/0
120308 11:03:28 [Note] NDB Binlog: ndb tables writable

But then when I try to create any NDB table it complains about the NDB storage engine not being available:

/opt/mysql/server-5.5/bin$ ./mysql -u root -P 5000
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 57
Server version: 5.1.58-1 (Debian)

mysql> create table t_test(test_id int) ENGINE=NDB;
Query OK, 0 rows affected, 2 warnings (0.06 sec)

mysql> SHOW WARNINGS;
+---------+------+------------------------------------------------+
| Level | Code | Message |
+---------+------+------------------------------------------------+
| Warning | 1286 | Unknown table engine 'NDB' |
| Warning | 1266 | Using storage engine MyISAM for table 't_test' |
+---------+------+------------------------------------------------+
2 rows in set (0.00 sec)

One thing I noticed is even though I connect to a 5.5 mysqld node,
the message refers to server 5.1 (which is the default install of mysql-server
via Debian that we have running on the standard 3306 port).

Is this the root cause of the issue? Is somehow mysql getting confused when having two different instances of MySQL running on the same box (on different ports)?

Thanks
Jacek