Why is the binlog file in the drainer data directory always empty when enabling binlog with db-type set to file and modifying or adding data?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 开启binlog，db-type为file，更改或新增数据，drainer data目录中的binlog文件一直为空文件，为何？

| username: TiDBer_fTFYIG4M

【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】
【Encountered Issue】After enabling binlog with db-type set to file, the binlog files in the drainer data directory remain empty when data is modified or added. Why is this happening? Using binlogctl to check the status of pump and drainer shows they are both normal.
【Reproduction Path】
Upgraded TiDB from v5.0.1 to v6.1.0 using tiup. TiFlash was upgraded by stopping the service as per the official documentation, while other components were upgraded without stopping. After the upgrade, the previously functioning binlog incremental logs stopped being output. Subsequently, binlog was redeployed using scale-in and scale-out, and the old binlog was cleared. Despite these steps, the binlog issue as described persists. How can this be resolved?
Drainer configuration:

drainer_servers:
  - host: 192.168.0.11
    data_dir: "/data1/db/tidb-data/drainer-8249"
    deploy_dir: "/data1/db/tidb-deploy/drainer-8249"
    # The following configs are used to overwrite the `server_configs.drainer` values.
    config:
      syncer.db-type: "file"
2
| username: 箱子NvN | Original post link

You can show the status of log-bin or check if any new features are used. It seems that binlog does not support some new features after version 5.0. You can refer to the official documentation for the precautions in the binlog introduction section.
TiDB Binlog Overview | PingCAP Docs

3
| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.