tiflow
tiflow copied to clipboard
cdc changefeed meet error: broken pipe
What did you do?
The CDC normally runs and synchronizes data to the downstream Kafka. Sometimes, there may be no data to synchronize from the upstream for more than 10 minutes. Then, during the next synchronization, the CDC receives an error from Sarama:
kafka async send message failed: kafka: Failed to produce message to topic xxx: write tcp IP:PORT->IP:PORT: write: broken pipe.
Then the changefeed lag will increase.
What did you expect to see?
The changefeed lag should be normal.
What did you see instead?
CDC receives broken pipe error, and changefeed lag increases.
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
v7.5.6
Upstream TiKV version (execute tikv-server --version):
v7.5.6
TiCDC version (execute cdc version):
v7.5.6