Oleksiy Kovyrin

Yet Another Admin's Blog

MySQL Proxy Released

Posted by Oleksiy Kovyrin under Databases, Development, My Projects

Few month ago I heard about some initial work on MySQL Proxy software by Jan Kneschke and I thought about implementing some type of MySQL Replication Aggregator based on this software. The idea was to create some piece of software which could get many replication streams, merge them and feed to some mysql slave. This software could be used for backup purposes and many other interesting things. But back then mysqlproxy distribution has been suspended (afaik, by MySQL AB because of some legal issues).

And at last, today MySQL Proxy project has been released to public and it became much more flexible so I think we need to take a look at it and try to implement such replication aggregator patches for it.

Related posts:

  1. MySQL Master-Master Replication Manager 1.0 Released
  2. MySQL Performance Blog – Отличный ресурс для администраторов MySQL
  3. Список 1000 (84) Лучших Советов по Производительности MySQL с MySQL Camp 2006
  4. MySql Больше не предоставляет бинарные сборки своим пользователям?
  5. InnoDB Recovery toolset Version 0.3 Released

7 Responses to this entry

shanon says:

Have recently been thinking of doing this as well, would enable one to join two or more ring replication setups into a larger ring. Very useful as it would make implementation of a fail over multi master geographic replication setup easy to deploy.

Gerry says:

How much overlap is there between MySQL-Proxy and MMM? I see load balancing in each. Can you provide examples of using these two technologies together?

Scoundrel says:

2Gerry: MMM is just monitoring/management software – it does not implements any load balancing – just high-availability.

As for using together – it is possible. For example, if your software could not use many reader connections or you want to balance your read load, you can join all reader IPs together and ask mysql-proxy to load-balance them.

Gerry says:

What does it monitor/manage? Just having db available on network? Or things like database health, replication delay? Is it automatically performing failover?

Scoundrel says:

It monitors all mysql servers in cluster and checks replication state, replication delay, mysql and IP connectivity. When something happens with one of cluster nodes, MMM tries to keep cluster alive.