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 …

This Thursday (November 6, 2008), Jay Pipes will guide you on a tour of Bazaar and Launchpad for beginners. Since Jay is located in Columbus, Ohio, this session will start later than usual, that is, at 17:00 UTC / 9:00am PDT / 12:00 EST / 17:00 BST / 18:00 CET.

Getting to know Bazaar and Launchpad is certainly interesting for most developers, but it's a "must-know" for anyone thinking of contributing code to MySQL, since MySQL development has been using Bazaar and Launchpad for quite a while now.

While I'm at it: 

On the eve of the Berlin Marathon a few weeks ago, I saw Santa Claus on skates, which reminded me …

IPC is over. My impression: The place was too big making it a little bit difficult to get in contact with others. Yet, from a technical and gastronomical point of view the Rheingoldhalle was a good choice. For the next IPC I would recommend to anker a hotel-ship near the hall (the Rheingoldhalle is situated at the bank of the river Rhine) to avoid a 30min shuttle bus ride from and to the hotel. ;-)

But back to my talk there.

The initial idea to this session was a performance consulting in spring this year: For a table with appr. 250 billion entries I found a way to store and read about 6,000 queries per second! I applied some very unusual ways to speed up a problem by factor 1,000 or 2,000 just by thinking about how I would do it, if I had to store the things in my home supposed they were real things such as cutlery.

I found out, that there are some patterns, which can …

Yesterday I was going through the locks related code; and found that in 5.0; when you have a global read lock; then the SHOW TABLE STATUS actually gets blocked when it had its own read lock on the new session; and this is not the case with MySQL 5.1

For example; lets execute the following set of statements in two sessions with MySQL 5.0 (latest bazaar version with InnoDB enabled):

Session 1:

mysql> use test;
Database changed
mysql> drop table if exists t1;
Query OK, 0 rows affected (0.07 sec)
 
mysql> create table test.t1(c1 int)Engine=InnoDB;
Query OK, 0 rows affected (0.00 sec)
 
mysql> flush tables with read lock;
Query OK, 0 rows affected (0.00 sec)

Session 2:

mysql> use test
Database changed
mysql> lock table t1 read;
Query OK, 0 rows affected (0.01 sec)
 
mysql> show …

Consider me a tomato.

Savio posted a MySQL needs to reconsider closed source article yesterday. I'm sure anyone who knows me knows that I'm one of the ones who is likely to be very vocally outraged if they do. I agree that the mythical "point #3" is the hard part of the general Open Source business plan ... although I'd put forward that #3 is always the hard part, Open Source or no. However, before I rant uncontrollably about that, I was struck by this:
Can you think of a better testament to the power of the open-source business model than saving Sun Microsystems?

Short answer:

Yes

First let's quibble over words again. If I answer the question the way it's intended to be answered (semi-rhetorically), it would be glossing over the gross error in assumption it …

Consider me a tomato.

Savio posted a MySQL needs to reconsider closed source article yesterday. I'm sure anyone who knows me knows that I'm one of the ones who is likely to be very vocally outraged if they do. I agree that the mythical "point #3" is the hard part of the general Open Source business plan ... although I'd put forward that #3 is always the hard part, Open Source or no. However, before I rant uncontrollably about that, I was struck by this:
Can you think of a better testament to the power of the open-source business model than saving Sun Microsystems?

Short answer:

Yes

First let's quibble over words again. If I answer the question the way it's intended to be answered (semi-rhetorically), it would be glossing over the gross error in assumption it …

As Sun's high-end systems revenue erodes, a re-think of taboo around MySQL's product strategy is needed. READ MORE

The mysqlbackup client program is now available for download as a feature preview. This program gives information about the produced backup image files and is a complement to the new MySQL 6.0 Backup feature. The program is not yet part of the main MySQL server releases.

So far, we have implemented the first milestone of WL#4534, e.g.:

• Display metadata contained in backup image (i.e the SQL statements)
• List objects contained in the backup image
• Display statistics about the backup image (e.g. compression algorithm)
• Search and display objects of backup image
• Search and display metadata of backup image objects
• In case of problems with reading the image provide as much information
  as possible, e.g. the position of the failure
  

The current preview …

Some time ago I get brand new IBM POWER6 server as the replacement for "old" P5 used to host Oracle database. Because we planed to use advanced virtualization with VIOS + LPAR/DLPAR I conceived the idea to use one spare partition for MySQL tests. Because I had no past experience with it and there is not much documentation all around the web, I tried to set-up system and database traditional way. The first problem I hit was memory allocation and I think it is the best place share my remarks. Let's start from the beginning..

For any reason, you decided to run MySQL database on AIX 5L operating system. You compiled it successfully, configured and.. unluckily database didn't start due to memory allocation problem?

Basically, for some historical reasons AIX OS will allow your application to allocate maximum 256MB of memory per process by default. To use more, you have to use "Large Address Space" memory model so AIX will split …

As promised, here are the DBT2 results for the Intel SSD drive:

As you see the Intel drive blew away all the competition here… even besting another dbt2 score I got from a nice new shiny 8 disk raid 10 system.