Closed alex-lx closed 5 years ago
Thanks for your feedback! PTAL @WangXiangUSTC
@alex-lx maybe a known issue fixed in later version, you can try to use the latest version from http://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz
@july2993 thanks for your kind help.
Since we use tidb-binlog
in our production, is the latest version production-ready? Is there any roadmap to release the fixed version and if any plan to backport the fix to v2.1.x?
already cherry pick this fix in v2.1.6, you can download from https://download.pingcap.org/tidb-v2.1.6-linux-amd64.tar.gz
Bug Report
Please answer these questions before submitting your issue. Thanks!
What did you do? Started drainer..
What did you expect to see?
The drainer process started successfully
It exited and print the following log
After setting log level to DEBUG, we can see the caused binlog is a ddl. ( We hide the real db name for privacy )
and the drainer has receive the ddl to create
db2
But it skip executing it without any log
tidb-server -V
or runselect tidb_version();
on TiDB)?v2.1.2