Aws lambda 执行AWS Lambda接收器连接器时出错

Aws lambda 执行AWS Lambda接收器连接器时出错,aws-lambda,apache-kafka-connect,confluent-platform,Aws Lambda,Apache Kafka Connect,Confluent Platform,我正在尝试执行AWS Lambda接收器连接器。我正在犯错误 [2021-04-21 02:01:39,104] INFO [AdminClient clientId=aws_lambda_sink-license-manager] Metadata update failed (org.apache.kafka.clients.admin.internals.AdminMetadataManager) org.apache.kafka.common.errors.TimeoutExceptio

我正在尝试执行AWS Lambda接收器连接器。我正在犯错误

[2021-04-21 02:01:39,104] INFO [AdminClient clientId=aws_lambda_sink-license-manager] Metadata update failed (org.apache.kafka.clients.admin.internals.AdminMetadataManager)
org.apache.kafka.common.errors.TimeoutException: Call(callName=fetchMetadata, deadlineMs=1618970499263) timed out at 9223372036854775807 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: The AdminClient thread has exited.
[2021-04-21 02:01:39,174] ERROR WorkerConnector{id=aws_lambda_sink} Error while starting connector (org.apache.kafka.connect.runtime.WorkerConnector)
org.apache.kafka.common.errors.TimeoutException: License topic could not be created
Caused by: org.apache.kafka.common.errors.TimeoutException: Call(callName=createTopics, deadlineMs=1618970499103) timed out at 1618970499104 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment.
下面给出了我的连接器配置

{
 "name": "aws_lambda_sink",
 "config": {
 "connector.class": "io.confluent.connect.aws.lambda.AwsLambdaSinkConnector",
 "tasks.max": "1",
 "topics": "mm.test.cecl.lambda",
 "aws.lambda.function.name": "kafka_lambda_sink_connector",
 "aws.lambda.invocation.type": "async",
 "aws.lambda.batch.size": "1",
 "aws.lambda.region": "us-east-1",
 "aws.access.key.id": "*************",
 "aws.secret.access.key": "***********",
 "behavior.on.error": "fail",
 "confluent.topic.bootstrap.servers": "sp-dev-broker-0.streawsnprd.massmutual.com:9092,sp-dev-broker-1.streawsnprd.massmutual.com:9092,sp-dev-broker-2.
streawsnprd.massmutual.com:9092,sp-dev-broker-3.streawsnprd.massmutual.com:9092,sp-dev-broker-4.streawsnprd.massmutual.com:9092,sp-dev-broker-5.streaws
nprd.massmutual.com:9092,sp-dev-broker-6.streawsnprd.massmutual.com:9092 ",
"reporter.bootstrap.servers": "sp-dev-broker-0.streawsnprd.massmutual.com:9092,sp-dev-broker-1.streawsnprd.massmutual.com:9092,sp-dev-broker-2.streawsn
prd.massmutual.com:9092,sp-dev-broker-3.streawsnprd.massmutual.com:9092,sp-dev-broker-4.streawsnprd.massmutual.com:9092,sp-dev-broker-5.streawsnprd.mas
smutual.com:9092,sp-dev-broker-6.streawsnprd.massmutual.com:9092 ",
 "consumer.override.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"kafka_connect\" password=\"*******\";"
}
}
是什么导致了这个问题


谢谢

您能够手动创建合流许可主题吗?否则,错误可能是SASL配置不适用于AdminClient,只有consumer@OneCricketeer_confluent-command主题已经存在。我正在使用kafka connect,它是sasl jaas配置中的管理员帐户。您在哪里为AdminClient配置了连接器sasl配置?@OneCricketeer我没有。我该怎么做?我建议尝试
admin.override.sasl.jaas.config
。但我不太确定,因为我没有使用连接SASL安全集群