We've now concluded our call for papers for the MySQL Developer Room at FOSDEM 2009 in Brussels, Belgium, which will be open on Sunday, 8th of February from 09:00-17:00.

We received some excellent proposals and I am very excited about the schedule. Here's the quick summary of the talks:

• Vladimir Kolesnikov: Practicing DBA's Guide to the PBXT Storage Engine
• Kris Buytaert: Monitoring MySQL
• Geert Vanderkelen: MySQL Cluster
• Roland Bouman: MySQL 5.1 Plugins
• Kaj Arnö: MySQL, powering and using Social Networks
• Ewen Fortune: Percona MySQL patches and the XtraDB storage engine
• Giuseppe Maxia: Boost performance with MySQL 5.1 partitions
• Jurriaan Persyn: Database Sharding

See the …

I've been working on some new options for ndb_restore which allows to include and exclude databases and/or tables while restoring. The current solution doesn't really work as documented, or isn't flexible enough.

Not really my job, but lots of us in MySQL Support are developers. Doing some coding from time to time keeps one sharp!

How it works? Let me show it with some (simplified) examples:

# only restore db1
ndb_restore --include-database="db1" /dir/.../
 
# only restore db2.t2 (1 table)
ndb_restore --include-tables="db2.t2" /dir/.../
 
# restore the rest of db2
ndb_restore --include-databases="db2" --exclude-tables="db2.t2" /dir/.../
 
# restore db3 excluding db1 and db2
ndb_restore --exclude-databases="db1,db2" /dir/.../

This isn't pushed yet, but if anyone has …

FOSDEM 2009, one of the biggest European Open Source conferences, will take place on February 7-8 in Brussels, Belgium. Today I received a confirmation from the organizers: MySQL will have a developer room on Sunday, the 8th! This is very cool.

My idea was to organize some kind of MySQL mini-conference, with a focus on developers and DBAs. I am going to send out a more formal CfP soon, but if you have any ideas or suggestions for a talks/sessions already, please get in touch with me!

In addition to the devroom, I have also been invited to give a talk about MySQL High Availability solutions in the conference main track. In this talk I plan to cover some commonly used HA setups for MySQL, including the OSS components/tools (for Linux and …

FOSDEM 2009, one of the biggest European Open Source conferences, will take place on February 7-8 in Brussels, Belgium. Today I received a confirmation from the organizers: MySQL will have a developer room on Sunday, the 8th! This is very cool.

My idea was to organize some kind of MySQL mini-conference, with a focus on developers and DBAs. I am going to send out a more formal CfP soon, but if you have any ideas or suggestions for a talks/sessions already, please get in touch with me!

In addition to the devroom, I have also been invited to give a talk about MySQL High Availability solutions in the conference main track. In this talk I plan to cover some commonly used HA setups for MySQL, including the OSS components/tools (for Linux and …

Here's a neat tip posted by Henrik Ingo from the MySQL Telecom Team

It's not really properly documented in the manual part, but I found in the changelogs, and confirmed on IRC that to do load-balancing across the SQL nodes in MySQL Cluster, you would use a different JDBC connection string with the "loadbalance" keyword added...

jdbc:mysql:loadbalance://host-1,host-2,...host-n/database?loadBalanceBlacklistTimeout=5000

ritu

The primary advantage of deploying the MySQL database in a Solaris Cluster environment is high availability. The Solaris Cluster environment provides fault monitoring and failover capabilities not only for the MySQL software, but also for the entire infrastructure including servers, storage, interconnects, and the operating system. If any component of the entire infrastructure fails, that failure is isolated and managed independently with no impact on availability.

MySQL Master-Slave configurations, deployed outside of a Solaris Cluster environment, provide limited availability: if the master fails, then the slave can manually be assigned master status and take over operation. However, this process is not automatic but requires manual intervention by a system administrator. Solaris Cluster removes this limitation, as it automatically fails over in the case of a master node failure. In addition, Solaris Cluster provides high …

ritu

The primary advantage of deploying the MySQL database in a Solaris Cluster environment is high availability. The Solaris Cluster environment provides fault monitoring and failover capabilities not only for the MySQL software, but also for the entire infrastructure including servers, storage, interconnects, and the operating system. If any component of the entire infrastructure fails, that failure is isolated and managed independently with no impact on availability.

MySQL Master-Slave configurations, deployed outside of a Solaris Cluster environment, provide limited availability: if the master fails, then the slave can manually be assigned master status and take over operation. However, this process is not automatic but requires manual intervention by a system administrator. Solaris Cluster removes this limitation, as it automatically fails over in the case of a master node failure. In addition, Solaris Cluster provides high …

ritu

The primary advantage of deploying the MySQL database in a Solaris Cluster environment is high availability. The Solaris Cluster environment provides fault monitoring and failover capabilities not only for the MySQL software, but also for the entire infrastructure including servers, storage, interconnects, and the operating system. If any component of the entire infrastructure fails, that failure is isolated and managed independently with no impact on availability.

MySQL Master-Slave configurations, deployed outside of a Solaris Cluster environment, provide limited availability: if the master fails, then the slave can manually be assigned master status and take over operation. However, this process is not automatic but requires manual intervention by a system administrator. Solaris Cluster removes this limitation, as it automatically fails over in the case of a master node failure. In addition, Solaris Cluster provides high …

One day we'll change some defaults to be more realistic, but in the meantime, please make sure you have set your FragmentLogFileSize and NoOfFragmentLogFiles to something big! Like, if you have 20Gb, set it the size to 256Mb and number of log files to 176, something like that (watch the diskspace though!). The thing his, if you need to restore your backup, you will run into problems and it just takes time, precious time to get it back up!
Anyway, those are not the only ones, and those hard hard to set later on (needs initial node restart, rolling though).

More in our all mighty manual and Johan's configuration tool.

Lenz just posted pointers to a great presentation of his about MySQL HA and Drupal,

Seems like a small part of me did go to Szeged afterall :)