MySQL NDB Cluster 7.2 Release Notes
Important Change:
When FILE
was used for the value of the
LogDestination
parameter
without also specifying the filename
, the log
file name defaulted to logger.log
. Now in
such cases, the name defaults to
ndb_
.
(Bug #11764570, Bug #57417)nodeid
_cluster.log
Packaging; Solaris: Some builds on Solaris 64-bit failed because the packages exceeded the 2GB limit for the SVR4 installation layout. Now such packages are built without the embedded versions of mysqltest and mysql-client_test to save space. (Bug #14058643)
Packaging; NDB Cluster APIs:
The file
META-INF/services/org.apache.openjpa.lib.conf.ProductDerivation
was missing from the clusterjpa
JAR file.
This could cause setting
openjpa.BrokerFactory
to
“ndb
” to be rejected.
(Bug #14192154)
References: See also: Bug #52106.
NDB Cluster APIs:
libndbclient
did not include the
NdbScanFilter
class.
(Bug #14010507)
NDB Cluster APIs:
When an NDB API application called
NdbScanOperation::nextResult()
again after the previous call had returned end-of-file (return
code 1), a transaction object was leaked. Now when this happens,
NDB returns error code 4210 (Ndb sent more info than
length specified); previouslyu in such cases, -1 was
returned. In addition, the extra transaction object associated
with the scan is freed, by returning it to the transaction
coordinator's idle list.
(Bug #11748194)
If the Transaction Coordinator aborted a transaction in the “prepared” state, this could cause a resource leak. (Bug #14208924)
When attempting to connect using a socket with a timeout, it was possible (if the timeout was exceeded) for the socket not to be set back to blocking. (Bug #14107173)
A shortage of scan fragment records in DBTC
resulted in a leak of concurrent scan table records and key
operation records.
(Bug #13966723)
Attempting to add both a column and an index on that column in
the same online ALTER TABLE
statement caused mysqld to fail. Although
this issue affected only the mysqld shipped
with MySQL NDB Cluster, the table named in the ALTER
TABLE
could use any storage engine for which online
operations are supported.
(Bug #12755722)