database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-08-05 13:16:09 +03:00
Code Activity

BUG#12818224: 61921: WRITETRAXINBINLOG SHOULD BE WRITETRANXINBINLOG

Browse Source 
IN SEMISYNC_MASTER.CC 

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

Additionally, fixed identation.
This commit is contained in:
Luis Soares
2011-09-08 11:10:26 +01:00
parent 74e7990a96
commit c77928b473
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
plugin/semisync/semisync_master.cc
View File

@@ -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.
* *
******************************************************************************/ ******************************************************************************/