Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: [cdc修改参数 CDC:ErrSinkInvalidConfig]sink config invalid: dispatcher and partition cannot be configured both](cdc修改参数 CDC:ErrSinkInvalidConfig]sink config invalid: dispatcher and partition cannot be configured both - TiDB 的问答社区)
|
username: wluckdog
[TiDB Usage Environment] Production Environment
[TiDB Version] v6.1.0
[Reproduction Path]
[Encountered Problem: Phenomenon and Impact]
CDC syncing to Kafka, write delay, CDC lag is relatively large.
After modifying max-batch-size, max-message-bytes, and worker-num for an already created CDC task, it fails to start with an error.
Parameter file:
case-sensitive = true
enable-old-value = true
[filter]
ignore-txn-start-ts = [1, 2]
rules = [‘test.t_test’]
[mounter]
worker-num = 16
[sink]
dispatchers = [
{matcher = [‘test.t_test’], dispatcher = “default”},
]
protocol = “canal-json”
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
Checked for large transactions on the source TiDB, none found, CDC task delay.
tiup cdc cli changefeed query -s --pd=http://127.0.0.1:2379 --changefeed-id=“t-test”
tiup is checking updates for component cdc …timeout!
Starting component cdc: /home/tidb/.tiup/components/cdc/v6.1.0/cdc cli changefeed query -s --pd=http://127.0.0.1:2379 --changefeed-id=t-test
{
“state”: “error”,
“tso”: 437202149934891161,
“checkpoint”: “2022-11-07 12:04:05.882”,
“error”: {
“addr”: “172.17.3.109:8300”,
“code”: “CDC:ErrSinkInvalidConfig”,
“message”: “[CDC:ErrSinkInvalidConfig]sink config invalid: dispatcher and partition cannot be configured both for rule:\u0026{[test.t-test] default default }”
}
}
After encountering the above error and failing to start, reverting the parameters to the default ones still does not work, reporting the same error.
|
username: 
|
username: 
|
username: