mysql-proxy 0.8.1 segfaults
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-proxy (CentOS) |
Invalid
|
High
|
|||
mysql-proxy (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Tested this on Ubuntu 12.10 x86_64
mysql-proxy 0.8.1-1.1build1 experiences a segfault under any load or after a few minutes of running idle (it is very fragile). I am getting the same occurrence with current EPEL (0.8.2-1.el6), although it seems to hold up for several seconds under mysqlslap. This tells me there is probably a bug in upstream mysql-proxy. The segfault occurs somewhere in libmysql-
mysql-proxy is the only useful way to do command splitting in a database cluster such that a single MySQL port served on 3306 on a single server will send non-transactional SELECT (read) statements to one server/port and all other statements to another server/port. With the two back-ends being haproxy with load balancing (for read) and fail-over (for write), this allows for spreading database reads across a high-availability cluster, while keeping writes directed at a single active master which fails over transparently.
Without mysql-proxy, only simple fail-over is possible. This directs all load to a single server and does not scale.
It is notable mysql-proxy is in Universe, so the above explanation of functionality does not elevate it above critical main packages.
Changed in mysql-proxy (CentOS): | |
importance: | Unknown → High |
status: | Unknown → Invalid |
Status changed to 'Confirmed' because the bug affects multiple users.