The problem with mysql-cluster

The problem with mysql-cluster is tricky-Linux Enterprise Application-Linux server application information. The following is a detailed description. I set up a mysql-cluster created by three servers.
Cluster version is 7.09g OS is RH-5.2-32
The RPM package installation method is used.
The servers are MySQL-Cluster-gpl-server and MySQL-Cluster-gpl-client and MySQL-Cluster-gpl-storage.
MGM is MySQL-Cluster-gpl-manm .. and MySQL-Cluster-gpl-tools
Setting up config. ini and my. cnf for speed is simple writing.
The output status of MGM is
Ndb_mgm> show
Cluster Configuration
---------------------
[Ndbd (NDB)] 2 node (s)
Id = 2 @ 192.168.187.138 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)
Id = 3 @ 192.168.187.139 (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)

[Ndb_mgmd (MGM)] 1 node (s)
Id = 1 @ 192.168.187.140 (mysql-5.1.39 ndb-7.0.9)

[Mysqld (API)] 3 node (s)
Id = 4 (not connected, accepting connect from any host)
Id = 5 (not connected, accepting connect from any host)
Id = 6 (not connected, accepting connect from any host)

No problems with services and ports
Mysql> show engines;
+ ------------ + --------- + ---------------------------------------------------------------- + ------------ +
| Engine | Support | Comment | Transactions | XA | Savepoints |
+ ------------ + --------- + ---------------------------------------------------------------- + ------------ +
| Ndbcluster | YES | Clustered, fault-tolerant tables | YES | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO |
| BLACKHOLE | YES |/dev/null storage engine (anything you write to it disappears) | NO |
| CSV | YES | CSV storage engine | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO |
| FEDERATED | NO | Federated MySQL storage engine | NULL |
| ARCHIVE | YES | Archive storage engine | NO |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO |
+ ------------ + --------- + ---------------------------------------------------------------- + ------------ +
You can create a database on NDB but an error is returned when you create a table.
Mysql> use test;
Database changed
Mysql> create table test111 (id int, name char (10) engine = ndbcluster;
ERROR 1005 (HY000): Can't create table 'test. test111' (errno: 157)
Mysql> show warnings;
+ ------- + ------ + ----------------------------------------------------------------------------------- +
| Level | Code | Message |
+ ------- + ------ + ----------------------------------------------------------------------------------- +
| Error | 1296 | Got error 4009 'Cluster failed' from NDB. cocould not acquire global schema lock |
| Error | 1296 | Got error 4009 'Cluster failed' from NDB |
| Error | 1005 | Can't create table 'test. test111' (errno: 157) |
+ ------- + ------ + ---------------------------------------------------

The error log is
091201 1:30:05 [Note] NDB: NodeID is 4, management server '192. 168.187.140: 661'
091201 1:30:06 [Note] NDB [0]: NodeID: 4, no storage nodes connected (timed out)
091201 1:30:06 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id
091201 1:30:06 [Note] Starting Cluster Binlog Thread
091201 1:30:07 [Note] Event schedents: Loaded 0 events
091201 1:30:22 [Warning] NDB: Tables not available after 15 seconds. Consider increasing -- ndb-wait-setup value
091201 1:30:22 [Note]/usr/sbin/mysqld: ready for connections.
Version: '5. 1.39-ndb-7.0.9-cluster-gpl 'socket: '/var/lib/mysql. sock' port: 3306 MySQL Cluster Server (GPL)
01:34:32 [NdbApi] INFO -- Management server closed connection early. it is probably being shut down (or has problems ). we will retry the connection. 110 Time out talking to management server Error line: 467
091201 02:01:12 mysqld_safe A mysqld process already exists
091201 2:02:15 [Warning] NDB: cocould not acquire global schema lock (4009) Cluster Failur


Master ~~