TiCDC actively checks the size of min.insync.replicas and replication-factor

[glkappe]

What did you do?

./cdc cli changefeed create --pd http://127.0.0.1:2379 --sink-uri "kafka://127.0.0.1:55426/ticdc-test2333?partition-num=1&replication-factor=1"

127.0.0.1:55426 is Amazon MSK Kafka Service

min.insync.replicas： 2 aws default，request-required-acks：-1 cdc default value，replication-factor: 1 sink-uri

What did you expect to see?

data in kafka's topic

What did you see instead?

[2021/12/16 18:42:38.578 +08:00] [ERROR] [feed_state_manager.go:240] ["processor report an error"] [changefeedID=simpledrvv-replicastions-taask-12345] [captureID=aa51a900-190-41fb-9201-e9c0c4357fe22] [error="{"addr":"1123123123213:8301","code":"CDC:ErrProcessorUnknown","message":"[CDC:ErrKafkaAsyncSendMessage]kafka: Failed to produce message to topic tidb_cdc_message: kafka server: Messages are rejected since there are fewer in-sync replicas than required.: kafka: Failed to produce message to topic tidb_cdc_message: kafka server: Messages are rejected since there are fewer in-sync replicas than required."}"]

Versions of the cluster

v5.2.2\v5.2.3

current status of DM cluster (execute query-status in dmctl)

(paste current status of DM cluster here)

[Rustin170506]

/assign