I have been fairly quiet on my blog for some time. We've been
very busy
developing new features for MySQL Cluster 7.5 and ensuring that
the
quality is improved even further.
We're now very pleased to release a new version of MySQL
Cluster.
MySQL Cluster 7.5 contains a number of new things that makes
MySQL
Cluster even better.
1) You can declare a table as a READ_BACKUP table. This means
that
the updating transactions will receive the commit
acknowledge
a little bit later to ensure that we can always use any of
the
replicas for reading. We will use the nearest replica for
committed reads, for locking reads we will still use the
primary
replica to avoid deadlocks.
For applications that are mostly read-focused one can make it
easier
to set this variable by setting the ndb-read-backup config
variable
to 1 in the MySQL Server …
The MySQL team at Oracle are excited to announce the immediate availability of the MySQL Cluster 7.5.4 GA release!
The development focus has been on improving overall performance and ease of use, combined with improved SQL support and the introduction of read optimized and fully replicated tables, all of which allow for better support of a variety of use cases.
The key enhancements delivered by MySQL Cluster 7.5 are summarized below:
Improved Performance: Improvements in index/range scan performance and internal thread handling will allow for better use of existing hardware and …
[Read more]How does an application configure its database connection? I find this to be a pretty interesting question. As the application moves from a developer’s workstation to a test harness, then to staging, and on to production, the database connection properties can change each time. …
I recently had the pleasure of attending the first OpenStack Days East conference in NYC. This was the first OpenStack Days event that we’ve had on the East Coast of the US, but I hope that it’s the first of many!…
Wrote this several months ago but was too busy to publish
:-/
As noted in one of the previous blog post, I will use following
terminology:
- "Processor" is a piece of hardware you connect to a socket on the motherboard.
- "Physical Core" is a physical computing unit built into the "Processor".
- "Virtual Core" is a virtual computing unit built on top of "Physical Core" (i.e. HT is ON).
- "CPU" is a computing unit inside the "Processor", either physical or virtual.
After a series of blogs on Windows performance counters and after
releasing sysb.ps1 testing/benchmarking framework
version 0.9RC (dbt2-0.37.50.10) I set out to eliminate some
unknowns from the testing. First to tackle …
I’m happy to announce that the third Development Milestone Release (DMR) of MySQL Cluster 7.5 — 7.5.2 — is now available!
Some highlights of this third milestone release of MySQL Cluster 7.5 are:
- This release is based on MySQL 5.7, so users can enjoy many of the great new features available in the latest MySQL Server, along with the many features that Cluster brings, including …
I’m happy to announce that the first Development Milestone Release (DMR) of MySQL Cluster 7.5 is now available!
Some highlights of this first milestone release of MySQL Cluster 7.5 are:
- This release is based on MySQL 5.7, so users can enjoy all of the great new features available in the latest MySQL Server, along with the many features that Cluster brings, including shared-nothing …
I recently worked a lot on getting my local Windows box to
compile Windows.
I got a lot of help from the below link that took me a few steps
towards the
solution.
http://www.chriscalender.com/resolving-the-bison-exe-m4-invalid-argument-error-when-building-mysqlmariadbxtradb-on-windows/
I had to save away my bison installation, uninstall it and then
also
go into a registry editor and remove the various links to the
Start Menu referring to
some help for Bison that had spaces in the registry. Resolving
this meant that I could
manually run bison on the files in the mysql tarball and get the
desired result. But it
was still not enough, I still had the same error when running a
full automatic compile.
So then I found the …
We just announced availability of MySQL Cluster Manager 1.4.0! In this post we’ll highlight some details of the MCM 1.4.0 release.
Based on MySQL 5.6 MySQL Cluster Manager is part of the commercial MySQL Cluster offering from Oracle. MCM 1.4.0 is now based on the tried and tested MySQL 5.6 release.…
MySQL Cluster Manager 1.4.0 is available for download from My Oracle Support.
More details are available in the the MCM 1.4.0 Release Notes.
Updated documentation is available here……