You may have read Bernd’s recent post that explained how to try out some new beta functionality for MySQL Cluster and wondered what kind of use you could put the new ndb$info to. ndb$info uses tables/views to give real-time access to a whole host of information that helps you monitor and tune your MySQL Cluster deployment. This article gives one example, extending MySQL Enterprise Monitor to keep an eye on the amount of free memory on the data nodes and then raise an alarm when it starts to run low – even generating SNMP traps if that’s what you need.

One of the features of MySQL Enterprise Monitor is that you can define custom data collectors and that those data collectors can run SQL queries to get the data. The information …

Read this post today, http://mysqlha.blogspot.com/2010/02/dude-where-is-my-link.html. And I was amazed to find that on mysql.com it was so hard to download the community version of MySQL Server.

On the home page, could see links for

• Enterprise Products
• Resources
• Consulting
• Training
• News and Events

Couldn't find a link for Community Server Download or something similar, I've been working with MySQL for over 5 yrs, I know that the downloads and most of the useful stuff for open source devs like me is on http://dev.mysql.com. The Developer Zone hosts the following for us

• Community Server Downloads
• Documentation …

InfiniDB has a sensible Enterprise/Community release process, which seems similar to what I suggested for MySQL. Its simplicity also stands in stark contrast to MySQL’s new release policy, which is hard to understand and has been confusing people.

The time has come for major performance improvements to the reporter, stats-gather, alerter, and client scripts. This means that I will be rewriting the scripts in Python. A couple of reasons for this; to cut down on the number of modules that are required for the installation process (which also makes distributing the client script [...]

A few days back MariaDB announced their first GA release (see Released: MariaDB 5.1.42), so it is time to start testing it and there is not better way to test any MySQL version in a control environment other than MySQL Sandbox. However Sandbox relies on the fact that the tarball and tarball target directory are prefixed with mysql, which is not true with MariaDB. So here are the 2 tricks I had to use to make it work out of the box.

These steps are explained to create a single sandbox, the tips can be extrapolated to any other configuration. Also, I am trying to avoid renaming any files and/or directories as to leave the packages as close to the original as possible.
Step 1: Use A Symlink For The TarballThe make_sandbox script will then …

I just about have all of the INFORMATION_SCHEMA replaced with Table Functions!

The big wins:
One Execution path (less bugs)
Simple interface, which means more langauges
Zero materialization happening
Less Code. This allows us to remove a lot of code (and single shot passes for particular use cases).

The data dictionary operates entirely off the proto system, so what you see is what we have. We use the table names stored within the proto so no translation ever happens. This is pretty handy for filesystems which do not preserve case (and we don't have to do anything to support them any longer).

You can also type "SELECT * FROM DATA_DICTIONARY.SCHEMAS".

There is no longer a "SCHEMATA" tables, just SCHEMAS. Want INDEXES? SELECT FROM INDEXES.

We will also be able to split up the tables that are from the SQL ANSI standard one from the ones that are not. …

In the previous post I described the first steps of a Python library for controlling the replication of large installations. The intention of the library is to provide a uniform interface to such installations and that will allow procedures for handling various situations to be written in a uniform language.

For the library to be useful, it is necessary to support installations that use different operating systems for the machines, as well as different versions of the servers. Specifically, it is necessary to allow some aspects of the system to vary.

• Depending on the operating system, or even just how the …

I wanted to quickly let you know our plan for maintaining both the Community Edition of InfiniDB as well as our Enterprise Edition. Our current intentions are the following:

The InfiniDB Community Edition (free and open source) will be the first to receive bug fixes and maintenance releases. We make the commitment to issue an updated maintenance version once per calendar month. These updates will be thoroughly tested by our own internal QA department to ensure they arRead More...

Today we made a change in the schedule of talks held in the MySQL Developer Room at FOSDEM 2010, swapping two talks. Change is:

• 12:15 CET - Giuseppe's 'Sharding for the Masses
• 14:25 CET - Geert's Connecting MySQL and Python (title also changed)

The printed booklets found at the conference will not reflect the change, but the printable schedule has already been updated.

Today we made a change in the schedule of talks held in the MySQL Developer Room at FOSDEM 2010, swapping two talks. Change is:

• 12:15 CET - Giuseppe's 'Sharding for the Masses
• 14:25 CET - Geert's Connecting MySQL and Python (title also changed)

The printed booklets found at the conference will not reflect the change, but the printable schedule has already been updated.