Bug #36779 unhandled type COM_REGISTER_SLAVE when use Proxy between master and slave
Submitted: 17 May 2008 21:20 Modified: 3 Jun 2009 14:56
Reporter: Sveta Smirnova Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Proxy: Core Severity:S2 (Serious)
Version:0.6.1, load balancer, r369 OS:MacOS
Assigned to: CPU Architecture:Any

[17 May 2008 21:20] Sveta Smirnova 
Description:
When tried to verify bug #34412 meet error "[debug] (command) unhandled type COM_REGISTER_SLAVE" after issuing START SLAVE

How to repeat:
1. Start proxy as
mysql-proxy --proxy-lua-script=./lib/rw-splitting.lua --plugins=proxy  --proxy-backend-addresses=master_host:master_port

2. Obtain master log information from master.

3. Connect to slave, run CHANGE MASTER command.

4. Run START SLAVE

5. Get

[debug] (command) unhandled type COM_REGISTER_SLAVE
2008-05-18 00:28:58: ((error)) plugin.c.3593: COM_(0x15) is not handled
Abort trap
[3 Jun 2009 14:56] Kay Roepke 
Running MySQL Proxy as a relay between a master and a slave is currently not supported.
It might be added as a feature in a future version, but current versions are not expected to work in this scenario.
[4 Jun 2009 5:42] Sveta Smirnova 
Lack of this feature limit usage scenarios available for MySQL Proxy. So I'd like to have it verified as feature request at least.
[4 Jun 2009 10:24] Kay Roepke 
I agree with making this a feature request, but there are more things to cover than just the issue described here.
For that reason I will create a new bug report to track it and link to that from here.
[4 Jun 2009 11:32] Kay Roepke 
The feature request is tracked by bug#45328.