Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refine error message caused by internal kafka failures #3422

Closed
neverchanje opened this issue Jun 23, 2022 · 1 comment
Closed

refine error message caused by internal kafka failures #3422

neverchanje opened this issue Jun 23, 2022 · 1 comment
Assignees

Comments

@neverchanje
Copy link
Contributor

Though this is indeed an internal error, the message is quite unfriendly to read. The error is user-facing. We should refine it and let users immediately know the cause and how to fix.

dev=> create materialized view ad_mv as select * from ad_source;
ERROR:  RPC error: GrpcStatus(Status { code: Internal, message: "internal error: Meta data fetch error: BrokerTransportFailure (Local: Broker transport failure)", metadata: MetadataMap { headers: {"content-type": "application/grpc", "risingwave-error-bin": "CAESX2ludGVybmFsIGVycm9yOiBNZXRhIGRhdGEgZmV0Y2ggZXJyb3I6IEJyb2tlclRyYW5zcG9ydEZhaWx1cmUgKExvY2FsOiBCcm9rZXIgdHJhbnNwb3J0IGZhaWx1cmUp", "date": "Thu, 23 Jun 2022 05:48:12 GMT", "content-length": "0"} }, source: None })
Internal Error: The connection to Kafka brokers ("127.0.0.1:29092") is broken, please check its availability.
@neverchanje
Copy link
Contributor Author

fixed by #4227

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants