MySQL v5.1.73 - can the binlog_format betweem Master & slave be different? We are in the process of testing MySQL replication before using it in production. The MySQL is being setup by Puppet in our case and I noticed that the binlog_format setting is different between master and slave. 

On master:

mysql&gt; show variables like 'binlog_format' \G
*************************** 1. row ***************************
Variable_name: binlog_format
        Value: ROW


On slave:

mysql&gt; show variables like 'binlog_format' \G
*************************** 1. row ***************************
Variable_name: binlog_format
        Value: STATEMENT


Once in a while, the replication breaks with an error similar to the following:


  Last_SQL_Error: Could not execute Delete_rows event on table
  test.pruning; Can’t find record in ‘pruning’, Error_code: 1032;
  handler error HA_ERR_KEY_NOT_FOUND; the event’s master log
  mysql-bin.000002, end_log_pos 1448


We don't know for sure whether this was caused due to the different binlog_format setting between the master &amp; slave.

Could the above error potentially be caused by this inconsistent setting? Should I change the slave to "row" based format? It is hard to reproduce the error so I am looking for the best practice we should be following and we are very new to MySQL.
The Error Message you received


  Last_SQL_Error: Could not execute Delete_rows event on table test.pruning; Can’t find record in ‘pruning’, Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event’s master log mysql-bin.000002, end_log_pos 1448


This message can come up when doing a DELETE query with row-based replication. Unfortunately, it is one of the disadvantages to row-based replication:


  
  Disadvantages of row-based replication
  
  
  RBR can generate more data that must be logged. To replicate a DML statement (such as an UPDATE or DELETE statement), statement-based replication writes only the statement to the binary log. By contrast, row-based replication writes each changed row to the binary log. If the statement changes many rows, row-based replication may write significantly more data to the binary log; this is true even for statements that are rolled back. This also means that taking and restoring from backup can require more time. In addition, the binary log is locked for a longer time to write the data, which may cause concurrency problems.


I have addressed something similar (error 1032 in my answer to 
MySQL master master replication, safe to delete rows on both masters?) where doing a DELETE query was the issue.

In your case, since the Slave is using STATEMENT, the row change is expected to be a precise match of PRIMARY KEYs between Master and Slave. On many occassions, it may not be the case. That is why error 1032 exists.

To play it safe,


use binlog_format=ROW on both Master and Slave
use binlog_format=MIXED on both Master and Slave
use binlog_format=STATEMENT on both Master and Slave
You could experiment with Master MIXED and Slave ROW. At the very least, avoid STATEMENT on the Slave if the Master is not STATEMENT.