By default, MySQL Cluster sends log data to a file but you can also send it to the console or to Syslog; this article explains how to send it to Syslog. The example given here is for LINUX.

In this example, I’ll use the “user” syslog facility name and so the first step is to make sure that syslog is configured to route those messages. If this hasn’t already been configured then add the following lines to /etc/rsyslog.conf:

# Log user messages to local files
user.*    /var/log/user

For the changes to take effect, restart the syslog service:

[root@ws1 etc]# service rsyslog restart
Shutting down system logger:                               [  OK  ]
Starting system logger:                                    [  OK  ]

Note that you should make those changes as root.

Still as root, start up a stream of  any additions to the new log file:

[root@ws1 etc]# tail -f /var/log/user

…

As part of “MySQL Sunday” at this year’s Oracle Open World, Mat Keep and I will be presenting on the latest MySQL Cluster features. We’ll be presenting at 15:30 (Pacific Time) on 19th September (the event starts with a key note at 12:30).

If you’re attending Oracle Open World then please indicate that you’d like to attend the MySQL Sunday when you register. If you aren’t planning to go to Oracle Open World but will be in the San Francisco area then buying a Discover pass (only $50 if you register by 16 July) will get you into the MySQL Sunday sessions. Register here.

For details on the presentations and speakers, check here.

We are pleased to announce the availability of the 1.5.1 RC 2 release of InfiniDB Community Edition.  We plan on this being our last release candidate before our 1.5 Final release in early July.  

This release includes a number of bug fixes that you can see at http://bugs.launchpad.net/infinidb.  You can download the latest InfiniDB binaries, source code, and updated documentation at: http://infinidb.org/downloads.  We welcome your feedback&...

<p>Imagine we have a user table in MySQL and similarly, a products table. Each user can now busily buy items. But this is not what this article is all about. This article is more about, that users can also favor articles they like. From a database point of view, this represents a <em>m:n</em> relation, which is resolved by an additional table. We now want to display a list of all products and all users who favor a specific article. In real world scenarios, this can be a really big amount of data, but let's bring an approximation later into play and focus on the main idea for the moment. In addition we want to know, if the person who is actually logged in into the system, already favors a certain product.</p>

Read the rest »

Geert made us aware that MySQL Cluster now provides the possibility to disable arbitration in order to use an external arbitration mechanism. This is a really important feature, because... well, not really, but only because I was the one who designed it :-)

Coming up with the concept and the two parameters Arbitration=WaitExternal and ArbitrationTimeout=n took a few weeks of discussion. Once we agreed on how to do it, I think JonasMagnus coded it in 20 minutes on the mezzanine floor of the Hyatt, Santa Clara. After that MySQL conference I soon resigned from Sun, so I had now idea what then happened to this feature.

read more

I'm pleased to announce the release of Spider storage engine version 2.21(beta).
Spider is a Storage Engine for database sharding.
http://spiderformysql.com/

The main changes in this version are following.
- Add table parameter "bka_mode" and "bka_engine".
- Add server parameter "spider_bka_mode" and "spider_bka_engine".
  This parameters are for improvement performance for using BKA and using a lot of conditions with IN clause and so on.

"mysql-5.1.44.slave-trx-retry.diff" is included in the source tar ball from this release.
mysql-5.1.44.slave-trx-retry.diff adds a option "slave_transaction_retry_errors". This parameter is used like "slave_transaction_retry_errors=1158,1159,2013,12701". Slave sql thread retries the transaction if slave sql thread encounters the errors at this parameter. Number of retries are at "slave_transaction_retries".

Please see …

Before we get started here, let me state that I am using Ruby 1.9.1 (I refuse to look back!), and that I have not tested this solution on Ruby 1.8.6, but it should work there as well, though I may have some 1.9-isms in my code. Should be easy enough to spot.

I am working on writing an application in Ruby that can talk to an Windows application that has an ActiveX COM Automation object exposed. Ruby is basically the wrapper so that I can access the application from the Linux side of the world. So, I am using Ruby’s DRb to bridge those worlds because, after all, I am the Linux Bloke!

Well, as you may have guessed, I ran into problems with this approach. I simply could not call the COM objects from a call initiated with DRb, though I could call them directly just fine. After scratching my head a bit, I figured it out.

The win32ole module that runs on the Windows side of the world in Ruby only …

The replay of this webinar is now available from http://www.mysql.com/news-and-events/on-demand-webinars/display-od-545.html

MySQL and memcached has become, and will remain, the foundation for many dynamic web services with proven deployments in some of the largest and most prolific names on the web. There are classes of web services however that are update-intensive, demanding real-time responsiveness and continuous availability. In these cases, MySQL Cluster provides the familiarity and ease-of-use of the regular MySQL Server, while delivering significantly higher levels of write performance with less complexity, lower latency and 99.999% availability. This webinar will discuss the use-cases for both approaches, and provide an insight into how MySQL Cluster is enabling users to scale their update-intensive web services.

The …

I managed to get an "early upgrade" of my iPhone 3GS to the iPhone 4 despite AT&T's best efforts.  I've had a couple of days using the new iOS 4 operating system on my 3GS and a couple of hours with the iPhone 4.  So here are a few highlights of the initial hands-on experience with more updates on the weekend.

Updated with additional information, video & photos.

Low-res video (VGA resolution):

Here's a gallery of additional photos from the iPhone 4:
(Double click to see larger versions.)

Upgrade Process

Other than AT&T's longstanding inability to deal with demand, the upgrade process is pretty simple.   I chased the UPS driver home to get my iPhone today and just plugged into the USB cable to restore my last iPhone 3GS backup.  That took about 20 minutes. …

With a few changes to InnoDB and MySQL I think I can get more than 100,000 disk reads/second from MySQL 5.1.47. InnoDB and MySQL continue to amaze me. This is a remarkable result.

Storage devices that support more than 100,000 IOPs can be purchased for commodity servers. This capacity is much more interesting when InnoDB can use all of it or when storage vendors give you a discount because your software can't use their capacity. My first tests were done with an 8-core server and I was able to get ~12,000 disk reads/second from InnoDB in MySQL 5.0.84 and ~18,000 reads/second from the InnoDB plugin in MySQL 5.1.47. My second tests were done on a 16-core server and I was able to get ~18,000 reads/second from 5.0.84, ~30,000 reads/second from …