Implement an option which will allow Percona Server to operate as binlog server

[Sveta Smirnova]

Currently if one wants to move read load from main master they should setup intermediary slave. If this is just a slave which receives and applies all updates it may use a lot of resources and require expensive disk, CPU and memory while it needs only good network in order to distribute binary logs further.

Alternative workaround is to have all tables on this intermediary slave to have engine Blackhole, but this requires manual conversion and also affected by such bugs as lp:1722789

What I propose here is to create an option: binlog-server, which will tell intermediary slave to connect to master, read its binary logs and store them without updating any table. Then all other slaves can just connect to this server as a master and get binary logs from it.

[markus_albe (markus-albe)]

+1... I had submitted similar request on this blueprint not long ago: https://blueprints.launchpad.net/percona-server/+spec/standalone-binlog-server

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2510