-
**Describe the bug**
When our Kafka cluster is under load, we sometimes see this error from our kafka.js consumer:
```
KafkaJSSASLAuthenticationError: SASL SCRAM SHA512 authentication failed: Req…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version: 02bd916
- Deployment mode(standalone or cluster): cluster
- MQ typ…
-
### Description
We should check all our existing Node instrumentation to see if we can easily emit breadcrumbs as well.
It is important not to tie this to spans, as these have no data when not sampl…
mydea updated
1 month ago
-
[kafka-node](https://github.com/SOHU-Co/kafka-node) is not active, I think it's better to move on a [new lib](https://kafka.js.org/) for Kafka transporter.
See:
[kafka-node](https://github.com/SOH…
-
Currently as much as possible, we depend on upstream system's properties to ensure our `exactly once` processing.
Take mysql / PG for instance, we need to depend on their WAL log.
If we provide ou…
-
Hello,
Regarding the `strimzi-kafka-cli`, how can we specify the bootstrap server details when using the `kfk console-producer` command?
When I try:
`kfk console-producer --topic my-topic -n strimz…
-
We are running python Kafka producer clients in a serverless environment (AWS Lambda python3.8 runtime) whereby (as per recommended best practices) we are sharing long-lived producer connections acro…
-
Hi
We are using your kafka module to connect to kafka. We are unable to connect
1. The user name and password when using SASL, is not remembered. Once userid and pssword are set and saved, we canno…
-
### Report
Keda version: keda:2.14.0
ghcr.io/kedacore/keda:2.14.0
kubenetes version: 1.29
keda TriggerAuth is unable to read the Secrets from AWS secretsManager though provided the correct sec…
-
**Describe the bug**
The container in `kafka-broker-receiver` reports error code 143 on startup.
The only logs are
```
Picked up JAVA_TOOL_OPTIONS: -XX:+CrashOnOutOfMemoryError
{"@timestamp":…