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

bug: Topic writer infinite try send message larger, then grpc limit #1660

Open
rekby opened this issue Feb 21, 2025 · 1 comment · May be fixed by #1676
Open

bug: Topic writer infinite try send message larger, then grpc limit #1660

rekby opened this issue Feb 21, 2025 · 1 comment · May be fixed by #1676
Assignees
Labels
bug Something isn't working

Comments

@rekby
Copy link
Member

rekby commented Feb 21, 2025

Bug Report

YDB GO SDK version: 3.99.13

transport/ResourceExhausted (code = 8, source error = "rpc error: code = ResourceExhausted desc = trying to send message larger than max (897772857 vs. 67108864)", address: "xxx", nodeID = 123) at `github.com/ydb-platform/ydb-go-sdk/v3/internal/conn.(*grpcClientStream).RecvMsg(grpc_client_stream.go:171)`"
@rekby rekby added the bug Something isn't working label Feb 21, 2025
@rekby rekby self-assigned this Feb 21, 2025
@rekby rekby linked a pull request Mar 7, 2025 that will close this issue
7 tasks
@rekby
Copy link
Member Author

rekby commented Mar 7, 2025

Decision:

  1. Split message before send to grpc stream
  2. Add option WithMaxGrpcMessageBytes for create topic writer. The option must be used for change grpc message size in sync with ydb.With(config.WithGrpcOptions(grpc.WithDefaultCallOptions(grpc.MaxCallSendMsgSize(maxGrpcMsgSize)))) and similar for driver.

Direct grpc option stored in internal grpc field and can't be detected authomatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant