Starting with MySQL 4.1.14, changes for MySQL Cluster can be found in the MySQL 4.1 Server Release Notes.
Functionality added or changed:
Bugs fixed:
(Bug #11132) Connections between data nodes and management
nodes were not being closed following shutdown of
ndb_mgmd.
(Bug #11050) ndb_mgm> show printed
incorrectly after master data node failure.
(Bug #10956) More than 7 node restarts with
--initial caused cluster to fail.
(Bug #9826) (Bug #10948) Schema change
(DROP TABLE,
ALTER TABLE) crashed HPUX and
PPC32.
(Bug #9025) Data nodes failed to restart on 64-bit Solaris.
(Bug #11166) Insert records were incorrectly applied by
ndb_restore, thus making restoration from
backup inconsistent if the binlog contained inserts.
(Bug #8918) (Bug #9363) (Bug #10711) (Bug #10058) (Bug #9025)
Cluster would time out and crash after first query; setting
DataMemory to more than 2GB prevented cluster from starting;
calling ndb_select_count() crashed the
cluster. (64-bit Unix OSes)
(Bug #10190) When making a backup of a cluster where
NumberOfReplicas was equal to 1, the
backup's metadata was corrupted. (Linux)
(Bug #9945) ALTER TABLE caused
server crash. (Linux/390)
(Bug #11133) A delete operation performed as part of a transaction caused an erroneous result.
(Bug #10294) Not allowing sufficient parallelism in cluster
configuration (for example,
NoOfTransactions too small) caused
ndb_restore to fail without generating any
error messages.
(Bug #11290) Setting TransactionInactiveTimeout= 0 did not result in an infinite timeout.
