Closed
Bug 403722
Opened 18 years ago
Closed 18 years ago
Setup MySQL Proxy for Bugzilla-EU instance
Categories
(mozilla.org Graveyard :: Server Operations: Projects, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: justdave, Assigned: xb95)
Details
For performance of Bugzilla for Europeans we should put a slave database server and a web server (or cluster vhost) in Amsterdam.
We can either give it a separate hostname that people in Europe can use, or if we can get transatlantic updates working, we could GSLB the IP addresses so you get whichever one you're closer to.
| Reporter | ||
Updated•18 years ago
|
Assignee: server-ops → justdave
Comment 1•18 years ago
|
||
I think this is right -
2 RHEL4 web servers - already production
mrz will build:
2 RHEL5 web servers
1 DB server - RHEL4 or 5?
| Reporter | ||
Comment 2•18 years ago
|
||
MySQL 5 can safely slave to a MySQL 4 master (just can't go back the other way), so go ahead and make the DB server rhel5.
| Reporter | ||
Comment 3•18 years ago
|
||
So this is up at https://bugzilla-eu.mozilla.org/ but it's not exactly speedy. The transatlantic trip to get to the master database apparently slows it down beyond usable.
There might be some hacks we can do to speed it up (offloading more of the traffic to the slave database) but it's going to require application changes to do it, and we'll have to be careful what gets offloaded to the slave to avoid breaking things.
Updated•18 years ago
|
Assignee: justdave → mark
| Assignee | ||
Comment 4•18 years ago
|
||
What are the machine names involved? (Databases, webservers, ...)
Status: NEW → ASSIGNED
| Assignee | ||
Comment 5•18 years ago
|
||
This is setup again, database is back up and running, and the site is configured to use the proper base URL...
Not sure if there are still speed problems though. Am investigating what kind of database connections it is making, to where, etc.
| Assignee | ||
Comment 6•18 years ago
|
||
Going to be doing an experiment on this:
Setting up MySQL Proxy on nldb01, setup to split out writes to the master, but proxy all reads to the local slave. This should improve performance, at the expense of more mid-airs in situations with slave lag, etc.
At present, there's no slave lag on the NL slave anyway, so this shouldn't prove to be a problem in practice. If MySQL Proxy works out well, this could be neat to use to do more splitting of traffic, i.e. sending all searches to a MyISAM slow slave, and convert the standard slave to InnoDB, etc.
Will keep this updated as it progresses...
| Assignee | ||
Comment 7•18 years ago
|
||
Been trying to get MySQL Proxy to work with the R/W Splitting. It seems to have issues with not being able to re-use connections. Given that this is 99% of the functionality that needs to work, it seems like something is grossly wrong.
I've emailed the author of the script and am trying to figure out where the problem is. Not really sure that there will be a response, I will keep working on it myself.
Updating the summary of this bug to match reality.
Summary: Put a Bugzilla slave database and webserver in the .nl colo → Setup MySQL Proxy for Bugzilla-EU instance
| Assignee | ||
Comment 8•18 years ago
|
||
Seems to be a known issue with MySQL Proxy, for further reading:
http://forums.mysql.com/read.php?146,197645,197645#msg-197645
I'm investigating another option: Dormando's Proxy for MySQL. Seems to do the same sort of thing, but also in a very, very alpha state and probably not ready enough for use. Something to look at though.
Next steps: going to give a few days to see how the support post works out, hopefully we can use MySQL Proxy at some point.
| Assignee | ||
Comment 9•18 years ago
|
||
Moving to Projects, MySQL Proxy is not going to help us at the moment, so another way has to be found (code changes to Bugzilla?) or MySQL Proxy has to release an update.
Component: Server Operations → Server Operations: Projects
| Assignee | ||
Comment 10•18 years ago
|
||
FYI, apparently MySQL Proxy doesn't work with our password hashing (old style) which is what was causing the problems. I've not tried working around this yet. Mostly just updating as FYI.
| Assignee | ||
Comment 11•18 years ago
|
||
Due to some other concerns, this project is not going forward as is. Will open a new ticket when we decide how to accomplish this.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•