-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Atlas Streams
we try to include error info from librdkafka in kafka error messages, like below:
AtlasStreamProcessing> sp.process(\\\{$source: {connectionName: "BadKafka", topic: "t1"}}) MongoServerError: Failed to start stream processor: Could not connect to the Kafka topic with kafka error code: -195, message: Local: Broker transport failure., [thrd:sasl_plaintext://kafka.0x333339.io:9092/bootstrap]: sasl_[plaintext://kafka.0x333339.io:9092/bootstrap]: Failed to resolve 'kafka.0x333339.io:9092': Name or service not known (after 38ms in state CONNECT), [thrd:sasl_plaintext://kafka.0x333339.io:9092/bootstrap]
but a customer $emit failed to return a good error message:
$emit to Kafka topic encountered error while connecting, kafka error code: -195, correlationID = 17e3ae11ed97f062045cbd0
- is related to
-
SERVER-93641 Kafka connection failures sometimes return bad error message
- Open