-----启动jdbc连接ElasticSearch

wget /usr/local http://packages.confluent.io/archive/5.2/confluent-5.2.0-2.11.tar.gz -P ~/Downloads/
tar -zxvf ~/Downloads/confluent-5.2.0-2.11.tar.gz -C ~/Downloads/
sudo mv ~/Downloads/confluent-5.2.0 /usr/local/confluent

wget https://cdn.mysql.com//Downloads/Connector-J/mysql-connector-java-5.1.48.tar.gz
tar -xzf  mysql-connector-java-5.1.48.tar.gz
sudo mv mysql-connector-java-5.1.48 mv /usr/local/confluent/share/java/kafka-connect-jdbc

然后

vim /usr/local/confluent/etc/kafka-connect-jdbc/source-quickstart-sqlite.properties

然后我修改了下面的属性

connection.url=jdbc:mysql://fdgfgdfgrter.us-east-1.rds.amazonaws.com:3306/trf
mode=incrementing
connection.user=admin
connection.password=Welcome123
table.whitelist=PANStatementInstanceLog
schema.pattern=dbo

上次我修改

vim /usr/local/confluent/etc/kafka/connect-standalone.properties

我修改了下面的属性

bootstrap.servers=b-3.205147-ertrtr.erer.c5.ertert.us-east-1.amazonaws.com:9092,b-6.ertert-riskaudit.ertet.c5.kafka.us-east-1.amazonaws.com:9092,b-1.ertert-riskaudit.ertert.c5.kafka.us-east-1.amazonaws.com:9092
key.converter.schemas.enable=true
value.converter.schemas.enable=true
offset.storage.file.filename=/tmp/connect.offsets
offset.flush.interval.ms=10000
plugin.path=/usr/local/confluent/share/java

当我列出主题时，我看不到为表名列出的任何主题。
错误消息的堆栈跟踪

[2020-01-03 07:40:57,169] ERROR Failed to create job for /usr/local/confluent/etc/kafka-connect-jdbc/source-quickstart-sqlite.properties (org.apache.kafka.connect.cli.ConnectStandalone:108)
[2020-01-03 07:40:57,169] ERROR Stopping after connector error (org.apache.kafka.connect.cli.ConnectStandalone:119)
java.util.concurrent.ExecutionException: org.apache.kafka.connect.runtime.rest.errors.BadRequestException: Connector configuration is invalid and contains the following 2 error(s):
Invalid value com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. for configuration Couldn't open connection to jdbc:mysql://****.us-east-1.rds.amazonaws.com:3306/trf
Invalid value com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. for configuration Couldn't open connection to jdbc:mysql://****.us-east-1.rds.amazonaws.com:3306/trf
You can also find the above list of errors at the endpoint `/{connectorType}/config/validate`
        at org.apache.kafka.connect.util.ConvertingFutureCallback.result(ConvertingFutureCallback.java:79)
        at org.apache.kafka.connect.util.ConvertingFutureCallback.get(ConvertingFutureCallback.java:66)
        at org.apache.kafka.connect.cli.ConnectStandalone.main(ConnectStandalone.java:116)
Caused by: org.apache.kafka.connect.runtime.rest.errors.BadRequestException: Connector configuration is invalid and contains the following 2 error(s):
Invalid value com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. for configuration Couldn't open connection to jdbc:mysql://****.us-east-1.rds.amazonaws.com:3306/trf
Invalid value com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. for configuration Couldn't open connection to jdbc:mysql://****.us-east-1.rds.amazonaws.com:3306/trf
You can also find the above list of errors at the endpoint `/{connectorType}/config/validate`
        at org.apache.kafka.connect.runtime.AbstractHerder.maybeAddConfigErrors(AbstractHerder.java:423)
        at org.apache.kafka.connect.runtime.standalone.StandaloneHerder.putConnectorConfig(StandaloneHerder.java:188)
        at org.apache.kafka.connect.cli.ConnectStandalone.main(ConnectStandalone.java:113)

        curl -X POST -H "Accept:application/json" -H "Content-Type:application/json" IPaddressOfKCnode:8083/connectors/ -d '{"name": "emp-connector", "config": { "connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector", "tasks.max": "1", "connection.url": "jdbc:mysql://IPaddressOfLocalMachine:3306/test_db?user=root&password=pwd","table.whitelist": "emp","mode": "timestamp","topic.prefix": "mysql-" } }'

是否需要架构注册表？
不可以。您可以在json记录中启用架构。jdbc源代码可以根据表信息为您创建它们

value.converter=org.apache.kafka...JsonConverter 
value.converter.schemas.enable=true

提到了zookeper，但我没有提到什么是kafkastore.topic=\u schema
如果要使用schema registry，应该使用 kafkastore.bootstrap.servers 是Kafka的地址，不是Zookeeper。所以移除 kafkastore.connection.url 请阅读所有属性的说明文件
我没有做任何关于模式的事情。
没关系。schemas主题在注册表首次启动时创建
我可以在一个ec2上创建两个连接器吗
是（忽略可用的jvm堆空间）。同样，Kafka连接文档中对此进行了详细说明。
使用独立模式，首先要传递connect worker配置，然后在一个命令中最多传递n个连接器属性
使用分布式模式，可以使用kafka connect restapi
https://docs.confluent.io/current/connect/managing/configuring.html
当我打开vim/usr/local/confluent/etc/kafka connect jdbc/source-quickstart-sqlite.properties时
首先，这是针对sqlite的，而不是mysql/postgres。您不需要使用快速启动文件，它们只是作为参考
同样，所有属性都有很好的文档记录
https://docs.confluent.io/current/connect/kafka-connect-jdbc/index.html#connect-jdbc公司
我确实安装了jdbc连接器，当我开始的时候，我得到下面的错误
下面是关于如何调试的更多信息
https://www.confluent.io/blog/kafka-connect-deep-dive-jdbc-source-connector/
如前所述，我个人建议尽可能使用debezium/cdc
用于rds aurora的debezium连接器

我猜您计划使用avro来传输数据，所以在启动kafka connect workers时不要忘记指定avroconverter作为默认转换器。如果您将使用json，那么就不需要模式注册表。
1.1 kafkastore.topic=_schema 您是否已启动自己的模式注册表？启动schema registry时，必须指定“schemas”主题。基本上，schema registry将使用这个主题来存储它注册的模式，如果出现故障，它可以从那里恢复它们。
1.2 jdbc connector installed and when i start i get below error 默认情况下，jdbc连接器仅适用于sqlite和postgresql。如果您希望它与mysql数据库一起工作，那么您也应该将mysql驱动程序添加到类路径中。
2.这取决于您如何部署kafka connect工作人员。如果您选择分布式模式（推荐），那么实际上不需要单独的cli。您可以通过kafka connect restapi部署连接器。
3.有另一个属性称为 table.whitelist 可以在其上指定模式和表。e、 g:表.白名单用户、产品、事务