If one update statement updated two tables: UPDATE tableA a, tableB b SET a.cell_code = 'A5', b.cell_code = 'A5' WHERE a.id =3226855 AND b.id = 3226855
In the binlog, there will be two contiunous TABLEMAP events and following the UPDATE_EVENT corresponding to the two tables TableMap AMap TableMap BMap UPDATE AUPDATE UPDATE BUPDATE If a DistributedCacheClient is used, the two UPDATE EVENT will be mapped to the same table(the latter BMap). It is an expected behavior according to the source code. I think it is a bug, we can fix it Thanks, Lei wangl...@geekplus.com.cn
