GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

MySQL 5.6 Threaded Replication - Write_rows Error

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • MySQL 5.6 Threaded Replication - Write_rows Error

    I'm attempting to use threaded replication w/ 5.6 (mixed binlog format) by executing:

    stop slave;
    set global slave_parallel_workers=5;
    start slave;


    This works for awhile, but eventually the following error occurs:

    Cannot execute the current event group in the parallel mode. Encountered event Write_rows, relay-log name ./mysqld-relay-bin.001994, position 166611162 which prevents execution of this event group in parallel mode. Reason: the event is a part of a group that is unsupported in the parallel execution mode.

    Does anyone know what the write_rows event is? I attempted to use mysqlbinlog to decode the transaction via:


    mysqlbinlog --start-position=166611162 --stop-position=166611163 -v --base64-output=DECODE-ROWS /var/data/mysql/3306/mysqld-relay-bin.001994

    Output:

    /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
    /*!40019 SET @@session.max_insert_delayed_threads=0*/;
    /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_ TYPE=0*/;
    DELIMITER /*!*/;
    # at 166611162
    #131221 8:28:40 server id 1323 end_log_pos 166611059 CRC32 0x22df9850 Write_rows: table id 84028 flags: STMT_END_F
    ### Row event for unknown table #84028DELIMITER ;
    # End of log file
    ROLLBACK /* added by mysqlbinlog */;
    /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
    /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/;


    But I am not sure what to make of it.

  • #2
    The "Row event for unknown table" error may happen while decoding relay log, while it never should happen for original binary log. That is because transactions (even very big) can never be written to more then one binary log (if the max size is exceeded), while big transactions can span multiple relay logs. This makes debugging difficult if whole transaction does not fit in single relay log. See this bug report: http://bugs.mysql.com/bug.php?id=60964

    Can you decode the corresponding event from the binary log on master?

    Comment

    Working...
    X