Doris unable to connect to AWS MSK (Kafka) via SASL_SSL #25039
Unanswered
mq-lionel
asked this question in
A - General / Q&A
Replies: 1 comment
-
|
@mq-lionel: Any news about it? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Issue
Doris fails to connect to MSK via SASL_SSL using the public access broker urls.
However, I can connect to and execute commands on MSK using
confluent-kafkawith python and Kafka CLIs on local machine and various EC2 machine. I'm sure I have created the topic in all 3 partitions and tested it locally and on EC2s. The username and password are correct too.We follow this "Deploy Docker Cluster Instruction" using
apache/doris:2.0.0_alpha-fe-x86_64image to explore Doris.Is it a bug or is there some installation or setup missing here?
Code
Exception:
Execution failed: Error Failed to execute sql: java.sql.SQLException: (conn=41) errCode = 2, detailMessage = Failed to get all partitions of kafka topic: hello-kafka. error: Waited 5 seconds (plus 172678 nanoseconds delay) for io.grpc.stub.ClientCalls$GrpcFuture@11ee7d1[status=PENDING, info=[GrpcFuture{clientCall={delegate=ClientCallImpl{method=MethodDescriptor{fullMethodName=doris.PBackendService/get_info, type=UNARY, idempotent=false, safe=false, sampledToLocalTracing=true, requestMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@4fa3c662, responseMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@1e0d8fac, schemaDescriptor=org.apache.doris.proto.PBackendServiceGrpc$PBackendServiceMethodDescriptorSupplier@26192bfe}}}}]]
Beta Was this translation helpful? Give feedback.
All reactions