Commit 1f0a24d8 authored by Luis Soares's avatar Luis Soares

BUG#12818224: 61921: WRITETRAXINBINLOG SHOULD BE WRITETRANXINBINLOG

IN SEMISYNC_MASTER.CC 

Fixing typo: writeTraxInBinlog() => writeTranxInBinlog() .

Additionally, fixed identation.
parent f6307b18
...@@ -312,18 +312,18 @@ int ActiveTranx::clear_active_tranx_nodes(const char *log_file_name, ...@@ -312,18 +312,18 @@ int ActiveTranx::clear_active_tranx_nodes(const char *log_file_name,
* The most important functions during semi-syn replication listed: * The most important functions during semi-syn replication listed:
* *
* Master: * Master:
* . reportReplyBinlog(): called by the binlog dump thread when it receives * . reportReplyBinlog(): called by the binlog dump thread when it receives
* the slave's status information. * the slave's status information.
* . updateSyncHeader(): based on transaction waiting information, decide * . updateSyncHeader(): based on transaction waiting information, decide
* whether to request the slave to reply. * whether to request the slave to reply.
* . writeTraxInBinlog(): called by the transaction thread when it finishes * . writeTranxInBinlog(): called by the transaction thread when it finishes
* writing all transaction events in binlog. * writing all transaction events in binlog.
* . commitTrx(): transaction thread wait for the slave reply. * . commitTrx(): transaction thread wait for the slave reply.
* *
* Slave: * Slave:
* . slaveReadSyncHeader(): read the semi-sync header from the master, get the * . slaveReadSyncHeader(): read the semi-sync header from the master, get the
* sync status and get the payload for events. * sync status and get the payload for events.
* . slaveReply(): reply to the master about the replication progress. * . slaveReply(): reply to the master about the replication progress.
* *
******************************************************************************/ ******************************************************************************/
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment