Ideas, releases, practical guides, and perspectives from the people building with MySQL.
The hiatus is over; I am reasonably settled at my new home. Therefore, HackMySQL.com is back to normal operation.
Parlez-vous le français? Je peux parler le français mais pas bien. Si vous voulez, on peut essayer à parler en français. Merci de votre patience.
In previous MySQL 6.0 alpha’s, the new Falcon engine didn’t handle ‘large’ transactions (meaning lots of rows inserted at one time) very well. You typically had to fall back to looping through the data with various commit points to get all the data inserted in a timely fashion.
The Falcon team should get some good kudos for putting out the latest alpha release that has much improved handling of large transactions. Below are just a few examples of large inserts on a Fedora Core box with a single CPU. Falcon was given a 200MB record cache size and InnoDB got a comparable 200MB buffer pool size.
mysql> show create table t_mG
*************************** 1. row ***************************
Table: t_m
Create Table: CREATE TABLE `t_m` (
`client_transaction_id` int(11) NOT NULL DEFAULT '0',
`client_id` int(11) NOT NULL DEFAULT '0',
`investment_id` int(11) NOT NULL DEFAULT '0',
`action` varchar(10) NOT NULL,
`price` …[Read more]
Cluster
This blog entry describes how to install MySQL clusters on
Solaris.
MySQL cluster consist of 3 seperate types of nodes:
The SQL nodes are the nodes that applications can connect to.
Internally SQL nodes connect to storage nodes to process
the queries and return the result set to the end client.
The storage nodes are controlled by management nodes. They do
most of the work in processing the queries.
Managment nodes manages the entire cluster. They start and stop
the data and SQL nodes and manage backups.
Lets start with the simplistic installation where all the nodes
of the cluster are on the same box. Of course this is not how you
would do a typical MySQL cluster installation...but this is just
to get a feel of what is involved in MySQL cluster …
Cluster
This blog entry describes how to install MySQL clusters on
Solaris.
MySQL cluster consist of 3 seperate types of nodes:
The SQL nodes are the nodes that applications can connect to.
Internally SQL nodes connect to storage nodes to process
the queries and return the result set to the end client.
The storage nodes are controlled by management nodes. They do
most of the work in processing the queries.
Managment nodes manages the entire cluster. They start and stop
the data and SQL nodes and manage backups.
Lets start with the simplistic installation where all the nodes
of the cluster are on the same box. Of course this is not how you
would do a typical MySQL cluster installation...but this is just
to get a feel of what is involved in MySQL cluster …
I’ve been asked by a number of people on how to do an upgrade from DRBD version 0.7 to DRBD 8. This upgrade does necessitate some minimal service down time, but it’s really not rocket science. And no, it does not force you to sync all of your data all over again.
Here’s my quick write-up.
An initial word of caution
Do not, I repeat do not attempt your upgrade unless you have at least read this blog entry to the finish.
Getting ready
First, you need to make sure that you have both your DRBD 8 userland binaries and kernel module ready to install. For our support customers, this means that you simply download two RPMs (or .debs) from our support web site. Make sure you have the right packages; you want those that match your system architecture and (for the kernel module) also your running kernel. Also, make sure you get …
[Read more]Quick experiment with online changing of enabling/disabling compressed backups and local checkpoints (LCPs).
Backup is incredibly trivial and correct (even have some nodes do compressed, some not).
LCPs are a bit trickier when it comes to restore… currently how the code sits is that a block using the compressed file interface in NDBFS must specify if it wants to use the compressed read/write interface or not. So when you have LCPs that differ in compressed/non-compressed than the current config file setting, you’re not going to be able to restore them (although setting CompressedLCP=1 should let you restore either compressed or non-compressed LCPs).
At some point, I’ll probably move AsyncFile (our async file IO class) to just use azio alway, and modify azio to be transparent for non-compressed files…. I just have to fix up azio for direct io.
this is the mysql
developers working hard at our developer conference in
heidelberg, germany.
okay, not really. this is just a shot of a park on the shores of
the neckar river in heidelberg, germany, taken while we were on a
boat back from our day-off excursion to the german raptor
research centre.
the whole set of photos has more of
heidelberg, and some of the birds from the research centre. but
no shots of any developers. you will have to wait for the
oktoberfest pictures for those.
my wife celia also posted her …
MySQL AB today announced its plans to optimize the MySQL Enterprise Server for the SAP NetWeaver® platform.
At the SAP® TechEd '07 event being held in Las Vegas this week, MySQL and SAP AG also announced that the sales and support of the MaxDB database will revert back to SAP, in order to unify the product's development, distribution and support under one organization. MaxDB (formerly SAP DB) is the database that powers SAP® Business ByDesign(TM), the company's recently-announced on-demand software solution for midsize companies -- in addition to SAP® Business Suite and SAP® Business All-in-One.
This release of MySQL Toolkit fixes some minor bugs, and adds major new functionality to MySQL Parallel Dump. Big News: MySQL Parallel Dump I wrote a lot more tests and cleaned up MySQL Parallel Dump a lot (fixed bugs with failed dumps not being reported, for instance) but the really big news is I added chunking functionality to it. Now you can say mysql-parallel-dump --chunksize 100000 and it will try to divide each table into chunks with 100,000 rows each.
I wanted to point out something that might not be obvious from the name: MySQL Parallel Dump can be used as a generic wrapper to discover tables and databases, and fork off worker processes to do something to them in parallel. That “something” can easily be invoking mysqlcheck – or any other program. This makes it really easy for you to do multi-threaded whatever-you-need-to-do on MySQL tables. Here’s how: mysql-parallel-dump [options] -- 'mysqlcheck --optimize %D %N' There are several things going on here: