MySQL HA: 1. Desirable – most of the time, 2. Needed – often enough, 3. Available – there are some good options out there. Typical solutions consist of: Heartbeat with DRBD on Linux. Although HB was introduced to Linux, it can be used on Solaris, FreeBSD and others without the DRBD but with other solutions. Sun Cluster, Veritas (commercial), MySQL Proxy (still in [...]

I just realized something else Chris has mentioned:

Since MySQL Proxy 0.7.0 is soon to be released, I thought another brief tutorial would be helpful.

Indeed, we are looking to properly release 0.7.0 soon™.

In case you are wondering what’s happening with MySQL Proxy and what the deal with the code’s new home is, please consider making some time for the web-seminar next week.

It’s free but registration is required.

We will also have Carlo Cabanilla talking about …

I just realized something else Chris has mentioned:

Since MySQL Proxy 0.7.0 is soon to be released, I thought another brief tutorial would be helpful.

Indeed, we are looking to properly release 0.7.0 soon™.

In case you are wondering what’s happening with MySQL Proxy and what the deal with the code’s new home is, please consider making some time for the web-seminar next week.

It’s free but registration is required.

We will also have Carlo Cabanilla talking about …

I just realized something else Chris has mentioned:

Since MySQL Proxy 0.7.0 is soon to be released, I thought another brief tutorial would be helpful.

Indeed, we are looking to properly release 0.7.0 soon™.

In case you are wondering what’s happening with MySQL Proxy and what the deal with the code’s new home is, please consider making some time for the web-seminar next week.

It’s free but registration is required.

We will also have Carlo Cabanilla talking about …

Since MySQL Proxy 0.7.0 is soon to be released, I thought another brief tutorial would be helpful. Today we ran across a good use case, and so I wanted to pass this along. If you’ve not used Proxy yet, this is a great opportunity to get your feet wet with it and some Lua.

When queries are routed though MySQL Proxy from various servers, the MySQL Server only sees that the query came from the machine Proxy is running on.

So when you are viewing output of SHOW PROCESSLIST, you have no way of telling what server a particular query originated from.

However, this could be very useful information to have, especially to determine which server a particular long-running query is coming from at that particular moment in time.

mysql> show processlist;
+----+------+-----------------+------+---------+------+-------+------------------+
| Id | User | Host            | db …

It’s done!

Even if it took a while, too long, really, we finally have the MySQL Proxy code out in the open, where it belongs.

As part of this effort, we would also like to make our development process more transparent. To that effect, we’ve also created a Launchpad team that serves as a discussion hub. It comes with a mailing list, reachable at mysql-proxy-discuss@lists.launchpad.net, where we hope to have some interesting discussions about where to take Proxy, what to implement in what way, and of course to offer advice to users.

There’s not much in terms of “process” yet and quite possibly (and hopefully) it will stay this way, but let me outline some of my hopes and plans for going forward:

Pushing directly into the branches …