Using CaptureChangeMySQL to extract binlog, do some translation and then put to 
another database with PutDatabaseRecord processor.
But there's always data inconsitency between destination database and souce 
database. To debug this, I have do the following settings. 
CaptureChangeMySQL only output one table. There's a field called order_no that 
is uniq in the table.
All the proessors are scheduled with only one concurrency.
No data balance between nodes. All run on primary node
After CaptureChangeMySQL, add a LogAttrubute processor called log1. Before 
PutDatabaseRecord, also add a LogAttrubute, called log2. 
For the inconsistent data, i can  grep the order_no in log1 and log2. 
For one specified order_no, there's total 5  binlog message. But in log1, 
there's only one message. In log2, there's 5, but the order is changed. 

position       type
201721167  insert (appeared in log1 and log2)
201926490  update(appeared only in log2)
202728760  update(appeared only in log2)
203162806  update(appeared only in log2)
203135127  update (appeared only in log2, the position number is smaller then 
privious msg)

This really confused me a lot.
Any insight on this?  Thanks very much.

Lei



[email protected]

Reply via email to