The latest from the MySQL community

One basic way of debugging the MySQL Cluster data nodes(ndbd) is with good old printf-style debugging. Ie. adding printouts of the variable you want to see, recompile, start the node(s) and run your tests. This is a bit tedious but very universal.

Support for printing is available using "ndbout", which has both C++ style and printf style. This functionality is implemented in storage/ndb/include/util/NdbOut.hpp

Here is an example from debugging BUG#37592, where I wanted to add printouts to "Dbtup::rebuild_page_free_list" to see how the pageId increases while the rebuild is running:

void
Dbtup::rebuild_page_free_list(Signal* signal)
{
  Ptr fragOpPtr;
  fragOpPtr.i = signal->theData[1];
  Uint32 pageId = signal->theData[2];
  Uint32 tail = signal->theData[3];
  ptrCheckGuard(fragOpPtr, …

Kaj's blog: http://blogs.mysql.com/kaj/2008/06/18/netbeans-as-ide-for-developing-mysql-itself/

Kaj's blog: http://blogs.mysql.com/kaj/2008/06/18/netbeans-as-ide-for-developing-mysql-itself/

The next release of Mac OS X, Snow Leopard, will have ZFS enabled by default. There’s a good article for the masses, at ZDNet on ZFS on Snow Leopard - do read it.

We all know running any form of server using HFS+ tends to be a bit of a joke. So, Snow Leopard Server will be where ZFS makes its debut. It won’t be long before regular users will want it in their Mac Pro’s and so on…

OS X as a deployment platform for production MySQL servers? This is not far off, I’m sure.

Below are a few more pictures from the Red Hat Summit and FUDCon last week.

Just to keep you comin' back for more, below is the list of podcasts from the events that I will be posting in upcoming days:

Podcasts to come/Posted

• Jim Whitehurst -- President and CEO of Red Hat -- …

Below are a few more pictures from the Red Hat Summit and FUDCon last week.

Just to keep you comin' back for more, below is the list of podcasts from the events that I will be posting in upcoming days:

Podcasts to come/Posted

• Jim Whitehurst -- President and CEO of Red Hat -- …

Here are my slides used for presentation at Red Hat Summit in Boston last week:

Zmanda: Open Source Backup (.odp open office format, 1.7MB)

I have *never* had this happen to me.

Maybe it’s because it’s MySQL 6.0.4, maybe it’s because it’s on Windows, or perhaps I am just up working too late.

I have seen mojibake before, but usually it is unintelligible. But this? After I post this I am backing away slowly from my computer.

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 6.0.4-alpha-community MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use test;
Database changed
mysql> create table bits (val bit);
Query OK, 0 rows affected (0.09 sec)

mysql> insert into bits (val) VALUES (1),(0),(1),(1),(0);
Query OK, 5 rows affected (0.05 sec)
Records: 5  Duplicates: 0  Warnings: 0

mysql> select * from bits;
+------+
| val  |
+------+
| ?    |
|      |
| ?    |
| ?    |
|      |
+------+
5 rows …

Red Hat releases Spacewalk. It is described as: “the upstream community project from which the Red Hat Network Satellite product is derived“. Congratulations to all whom have worked on it, especially my friends who tired endlessly over it in the past.

Red Hat, is sticking true to its promise, of open sourcing everything they make. Best of all, they recognise Fedora (they always did, since say, Fedora Core 2 or 3), CentOS (a direct “competitor”/rebuild of RHEL), and Scientific Linux (I know of a certain university’s sysadmin who will be blessing Spacewalk, as her life will now be a lot easier).

There have been a few blogs about it… Matt Asay asks about a community (Red Hat traditionally wasn’t good at this, but with Fedora, I believe they’ve learned, and I’m happy …

KEY ACCOMPLISHMENTS LAST WEEK

• Set up automated runtime information collection tasks on 6 machines; These machines are compiling and testing MySQL 24/7 and uploading the results to Skoll server for future analysis.
• Modified Skoll's upload manager and data processor to handle the separate log files collected by the new Skoll Client. The separate log files include a Skoll Client log and a set of logs for each command (e.g. configure, compile, test) in a test run. The command logs are zipped together by the client before uploading to the server.

KEY TASKS THAT STALLED LAST WEEK

• None

KEY CONCERNS

• Future progress of the project depends on have push-build tar balls.

TASKS IN THE UPCOMING WEEK

• Add more information from the separate log files to the HTML results pages; this task would require database changes to Skoll server. …