Mysql log_slave_updates Parameters

website Description: Normally, a slave does not Log  toits ownbinary Log  anyUpdates that is received froma master server. ThisoptionTells the slave to LogThe updates performed byIts SQL thread toits ownbinary Log. forThisoption  toHave anyeffect, the slave must also be started withThe--log-bin option to enable binary logging. Prior to MySQL 5.5, the server would not start when using the--log-slave-updates option without also starting the server With the--log-bin option, and would. Fail with an error; In MySQL 5.5, only a warning is generated. (Bug #44663)--log-slave-updates is used if you want to chain replication servers. For example, you might want to set up replication servers using this arrangement:A -B -Chere, A serves asThe Master forThe slave B, andB serves asThe Master forThe slave C. forThis to  Work, B must be both a master anda slave. You must start both A andB with --Log-bin to enable binary logging, and B with the--log-slave-updates option so then updates received from A is logged By B-to-its binary log.Typically, updates received from the server from the primary server are not credited to its binary log. This option tells the server to log updates from its SQL thread into its own binary logs from the server. To make this option effective, you must also use the--The logs-bin option starts from the server to enable binary logging. If you want to apply a chained replication server, you should use--logs-slave-updates. For example, you might want to set this up:A -B -c that is, A is the primary server from Server B and B is the primary server from server C. To be able to work, B must be both the primary server and the slave server. You have to use--Logs-bin Start A and B to enable binary logging, and start B with the--logs-slave-updates option. 

This allows transactions from a to be recorded in a binary file of B and sent to C

Mysql log_slave_updates Parameters