Dear MySQL users,
MySQL Cluster is the distributed, shared-nothing variant of MySQL. This
storage engine provides:
- Real-time performance based on in-memory storage (with
checkpointing to disk)
- Read & write scalability through transparent auto-sharding
- 99.999% High Availability with no single point of failure and
on-line maintenance
- SQL and NoSQL API (including C++, Java, and http)
- Active-Active/Multi-Master geographic replication
MySQL Cluster 7.1.33, has been released and can be downloaded from
http://www.mysql.com/downloads/cluster/
where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.
The release notes are available from
http://dev.mysql.com/doc/relnotes/mysql-cluster/7.1/en/index.html
MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.
More details can be found at
http://www.mysql.com/products/cluster/
Enjoy !
Changes in MySQL Cluster NDB 7.1.33 (5.1.73-ndb-7.1.33) (2014-10-21)
MySQL Cluster NDB 7.1.33 is a new release of MySQL Cluster,
incorporating new features in the NDB storage engine and fixing
recently discovered bugs in previous MySQL Cluster NDB 7.1
releases.
The latest MySQL Cluster NDB 7.1 binaries for supported platforms
can be obtained from http://dev.mysql.com/downloads/cluster/.
Source code for the latest MySQL Cluster NDB 7.1 release can be
obtained from the same location.
You can also access the MySQL Cluster NDB 7.1 development source
tree at https://code.launchpad.net/~mysql/mysql-server/cluster-7.1
This release also incorporates all bugfixes and changes made in
previous MySQL Cluster releases, as well as all bugfixes and
feature changes which were added in mainline MySQL 5.1 through
MySQL 5.1.73 (see Changes in MySQL 5.1.73 (2013-12-03)
(http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-73.html))
.
Functionality Added or Changed
* Added the --exclude-missing-tables option for ndb_restore.
When enabled, the option causes tables present in the backup
but not in the target database to be ignored. (Bug #57566, Bug
#11764704)
Bugs Fixed
* When assembling error messages of the form Incorrect state for
node n state: node_state, written when the transporter failed
to connect, the node state was used in place of the node ID in
a number of instances, which resulted in errors of this type
for which the node state was reported incorrectly. (Bug
#19559313, Bug #73801)
* In some cases, transporter receive buffers were reset by one
thread while being read by another. This happened when a race
condition occurred between a thread receiving data and another
thread initiating disconnect of the transporter (disconnection
clears this buffer). Concurrency logic has now been
implemented to keep this race from taking place. (Bug
#19554279, Bug #73656)
* A more detailed error report is printed in the event of a
critical failure in one of the NDB internal sendSignal*()
methods, prior to crashing the process, as was already
implemented for sendSignal(), but was missing from the more
specialized sendSignalNoRelease() method. Having a crash of
this type correctly reported can help with identifying
configuration hardware issues in some cases. (Bug #19414511)
References: See also Bug #19390895.
* ndb_restore failed to restore the cluster's metadata when
there were more than approximately 17 K data objects. (Bug
#19202654)
* Parallel transactions performing reads immediately preceding a
delete on the same tuple could cause the NDB kernel to crash.
This was more likely to occur when separate TC threads were
specified using the ThreadConfig configuration parameter. (Bug
#19031389)
* Incorrect calculation of the next autoincrement value
following a manual insertion towards the end of a cached range
could result in duplicate values sometimes being used. This
issue could manifest itself whne using certain combinations of
values for auto_increment_increment, auto_increment_offset,
and ndb_batch_prefetch_sz.
This issue has been fixed by modifying this calculation to
ensure that the next value from the cache as computed by NDB
is of the form auto_increment_offset + (N *
auto_increment_increment. This avoids any rounding up by the
MySQL Server of the returned value, which could result in
duplicate entries when the rounded-up value fell outside the
range of values cached by NDB. (Bug #17893872)
* ndb_show_tables --help output contained misleading information
about the --database (-d) option. In addition, the long form
of the option (--database) did not work properly. (Bug
#17703874)
* Using the --help option with ndb_print_file caused the program
to segfault. (Bug #17069285)
* For multithreaded data nodes, some threads do communicate
often, with the result that very old signals can remain at the
top of the signal buffers. When performing a thread trace, the
signal dumper calculated the latest signal ID from what it
found in the signal buffers, which meant that these old
signals could be erroneously counted as the newest ones. Now
the signal ID counter is kept as part of the thread state, and
it is this value that is used when dumping signals for trace
files. (Bug #73842, Bug #19582807)
* Cluster API: The fix for Bug #16723708 stopped the
ndb_logevent_get_next() function from casting a log event's
ndb_mgm_event_category to an enum type, but this change
interfered with existing applications, and so the function's
original behavior is now reinstated. A new MGM API function
exhibiting the corrected behavior ndb_logevent_get_next2() has
been added in this release to take the place of the reverted
function, for use in applications that do not require backward
compatibility. In all other respects apart from this, the new
function is identical with its predecessor. (Bug #18354165)
* ClusterJ: Retrieval of values from BLOB and TEXT columns by
ClusterJ column accessor methods was not handled correctly.
(Bug #18419468, Bug #19028487)
On Behalf of The Oracle/MySQL RE Team,
Sunanda Menon
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
