search

bigcy / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

RENAME TABLE statement issue #357

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Setup bi-directional replication
2. Try to rename any table

What is the expected output?

Table should be renamed

What do you see instead?

No any changes
Here is list seqno output:

SEQ# = 15333 / FRAG# = 0 (last frag)
- TIME = 2012-08-03 05:23:48.0
- EPOCH# = 9985
- EVENTID = bin-log.000006:0000000013642494;0
- SOURCEID = db3
- METADATA = 
[mysql_server_id=427555;unsafe_for_block_commit;bidi_unsafe=true;service=db3;sha
rd=#UNKNOWN]
- TYPE = com.continuent.tungsten.replicator.event.ReplDBMSEvent
- OPTIONS = [##charset = UTF-8, autocommit = 1, sql_auto_is_null = 0, 
foreign_key_checks = 1, unique_checks = 1, auto_increment_increment = 2, 
auto_increment_offset = 3, sql_mode = '', character_set_client = 33, 
collation_connection = 33, collation_server = 8]
- SCHEMA = movado_prod
- SQL(0) = rename table core_config_data_dizel123 to core_config_data_1123 /* 
___SERVICE___ = [db3] */

What version of the product are you using?

tungsten-replicator-2.0.6-733

On what operating system?

Red Hat Enterprise Linux Server release 6.1

Please provide any additional information below.

Notes:

Mysql 5.5.25a

Original issue reported on code.google.com by asuprune...@gorillagroup.com on 3 Aug 2012 at 10:46

GoogleCodeExporter commented 9 years ago 
bug also apply on version 2.0.5 b551

Original comment by sfout...@gmail.com on 28 Sep 2012 at 10:17

GoogleCodeExporter commented 9 years ago 
This looks like a possible problem with the filtering to suppress unsafe SQL 
that might create loops.  The rename command is not supported in the regex 
parser for statements. 

For now I suggest running rename on each affected host.

Original comment by robert.h...@continuent.com on 7 Oct 2012 at 7:13

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hello, 
on 2.0.5 replication was broken by the rename command.

on 2.0.6 build 889
the bug has changed.
now the rename table is logged on slaves, the replication is not broken but the 
rename table is not executed on slaves.

Don't know which one is worse :(

Original comment by sfout...@gmail.com on 3 Apr 2013 at 9:34