I was wondering how many use mysql proxy “in the middle” in order to get Query Analyzer functionallity? This is really all I want it for. I’m at a crossroads trying to decide if going forward want to start implimenting mysql agent “in the middle” on all our production databases to get the Query Analyzer functionality. The main drawbacks I’ve found are the following:

- Upgrading the agent requires downtime
- Not able to use IP level access control on user accounts. Have to use ‘webuser’@'%’ for example.
- Not able to see what servers users are logging in from since all logins are from the agent and are displayed as “localhost” in the processlist.
- If agent crashes, access to database is lost.
- Increased overhead.

I’m just not sure it’s worth it!!

Just wondering what others are doing. Is MySQL Agent used “in the middle” commonly in production databases?

Thanks!

If it leads to 2-3x overheads, is there another alternative to deal with that ?

Informative post, but it wasn’t clear to me whether the you used some kind of connection pooling? I.e. is the performance bad because of connection creation, or will the penalty effect each query run thru an open connection.

Try Tungsten Connector. (http://www.continuent.com/community/tungsten-connector) It’s written in Java and schedules threads efficiently across multiple cores.

Also, what do you need Lua for? If you provide a use case we can look at how to get it for you. We have a lot of work afoot in this area, for example implementing session consistency load balancing.

Cheers, Robert

I did not try ha-proxy, it seems it does not support functionality I need, I am looking to handle coming queries in one specific way.

It was long time ago and was very early releases, so I do not remember all details. Can’t say it was in previous release.

I will try recent trunk.
Current run was without Lua scripts, but actually I am looking to add some scripts, we I need Lua…