TiCDC 6.5.0 无法接入 sasl 的kafka集群

TiCDC 无法接入 sasl 的kafka,有人遇到过吗?麻烦帮忙看一下

tiup cdc:v6.5.0 cli changefeed create -c mxxxxx-xxxxx-test --pd=http://xxxxx:3379 --sink-uri="kafka://kf1xxxxxx.com:9092,kf2xxxxxx.com:9092,kf3xxxxxx.com:9092/reader-test.mxxxxx.shbt.ticdc?protocol=canal-json&enable-tidb-extension=true&kafka-version=2.5.1&partition-num=3&kafka-client-id=producer_ticdc-prod_mxxxx_xxxxx_test&max-message-bytes=8388608&replication-factor=2&sasl-user=ticdc-prod&sasl-password=xxxx\$xxxx&sasl-mechanism=SCRAM-SHA-256"  --sort-engine="unified" --config=task_test65.yaml
Starting component `cdc`: /home/tidb/.tiup/components/cdc/v6.5.0/cdc /home/tidb/.tiup/components/cdc/v6.5.0/cdc cli changefeed create -c mxxxxx-shbtcore-test --pd=http://xxxxx:3379 --sink-uri=kafka://kf1xxxxxx.com:9092,kf2xxxxxx.com:9092,kf3xxxxxx.com:9092/reader-test.mxxxxx.shbt.ticdc?protocol=canal-json&enable-tidb-extension=true&kafka-version=2.5.1&partition-num=3&kafka-client-id=producer_ticdc-prod_mxxxx_xxxxx_test&max-message-bytes=8388608&replication-factor=2&sasl-user=ticdc-prod&sasl-password=xxxx$xxxx&sasl-mechanism=SCRAM-SHA-256 --sort-engine=unified --config=task_test65.yaml
[WARN] some tables are not eligible to replicate, []v2.TableName{v2.TableName{Schema:"xxxxx", Table:"xxxxx", TableID:2184, IsPartition:false}, v2.TableName{Schema:"xxxxx", Table:"xxxxx", TableID:2282, IsPartition:false}, v2.TableName{Schema:"xxxxx", Table:"flowstatus", TableID:2470, IsPartition:false}, v2.TableName{Schema:"xxxxx", Table:"location_search", TableID:2610, IsPartition:false}, v2.TableName{Schema:"xxxxx", Table:"xxxx", TableID:2612, IsPartition:true}, v2.TableName{Schema:"xxxxx", Table:"logs", TableID:2803, IsPartition:true}, v2.TableName{Schema:"xxxxx", Table:"size_type", TableID:3094, IsPartition:false}, v2.TableName{Schema:"xxxxx", Table:"xxxxx", TableID:3122, IsPartition:false}}
Could you agree to ignore those tables, and continue to replicate [Y/N]
Y
Error: [CDC:ErrKafkaNewSaramaProducer]new sarama producer: kafka server: The client is not authorized to send this request type

有没有可能是密码的$符号的影响呢

确实,我之前遇到过“#”号不行的问题,建议楼主把密码的特殊字符干掉再试试

看着确实像sasl密码有问题

是不是配置没填完整?

红框里的都得配置么

你这看上去就像授权没 通过,感觉是你密码有特殊字符,你换个密码试试看

应用的环境给到你的配置信息是什么,就都要填进去了

经测试,是密码中含有特殊字符,sink 参数 sasl-password 对特殊字符处理的逻辑有待完善。5.4 和 6.5 都有相同的问题,用户在设置密码中不可避免采用特殊字符,希望兼容

感觉可能是代码问题,我之前dm也出现过一样的问题,特殊字符底层应该需要转义符处理一下

这种其实应该是bash对特殊字符的处理有关系,你试下用单引号,而不是双引号

此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。