prad9
commented
1 year ago Same issue connecting to Confluent cloud hosted cluster from producer. This is intermittent issue but doesn't happen all times
kafkajs: 2.1.0 @kafkajs/confluent-schema-registry: 3.3.0
Configuration:
const sasl: SASLOptions = {
username: secrets.kafkaClusterApiKey,
password: secrets.kafkaClusterApiSecret,
mechanism: "plain",
};
const kafkaConfig: KafkaConfig = {
clientId: clientId,
brokers: [kafkaClusterEndpoint],
ssl: true,
sasl,
};
const kafka = new Kafka(kafkaConfig);
const producer = kafka.producer({ createPartitioner: Partitioners.DefaultPartitioner });
logger.info("Kafka producer created");
await producer.connect();Error logs:
{
"level": "ERROR",
"timestamp": "2023-03-27T02:34:39.463Z",
"logger": "kafkajs",
"message": "[Connection] Connection error: Client network socket disconnected before secure TLS connection was established",
"broker": "****:9092",
"clientId": "agents-call-data-collection",
"stack": "Error: Client network socket disconnected before secure TLS connection was established\n at connResetException (internal/errors.js:639:14)\n at TLSSocket.onConnectEnd (_tls_wrap.js:1570:19)\n at TLSSocket.emit (events.js:412:35)\n at endReadableNT (internal/streams/readable.js:1333:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)"
}
2023-03-27T02:34:39.463Z bb588c6d-58e6-44ba-abf5-aef5d106a4dc ERROR
{
"level": "ERROR",
"timestamp": "2023-03-27T02:34:39.463Z",
"logger": "kafkajs",
"message": "[BrokerPool] Failed to connect to seed broker, trying another broker from the list: Connection error: Client network socket disconnected before secure TLS connection was established",
"retryCount": 0,
"retryTime": 334
}```
dhvidding-accenture
Borduhh
cjnoname
alvincrisuy
Describe the bug We see inconsistent connection/authentication timeouts when using AWS Lambda Producers via KafkaJS and MSK.
To Reproduce
NOTE: We can consistently produce the error in our technical stack but cannot produce the error using a minimum repo
Example Lambda Code:
Example Kafka Middleware:
Expected behavior The producer should connect to the MSK cluster without an issue.
Observed behavior Lambda Logs:
MSK Broker Logs:
Environment:
Additional context The weird part is that we load tested a simple repo with the same code with 30+ lambdas and 4K messages, and it worked as expected, although we manually invoked the lambda.