-
Notifications
You must be signed in to change notification settings - Fork 616
GRPC max size? #1755
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
Comments
@garye does this sound right? I was looking around in the v2 files just now and the closest thing I found was mention of a max insertion of 100000 mutations. |
I think they're hitting a gRPC limit, not a bigtable limit. This is meant to be consistent across grpc implementations: The workaround is to just send smaller individual requests - any individual bulk mutation, for example, should be < 4MB. |
@callmehiphop can we add a mention in the docs to slice up large requests to avoid this error? |
@garye is there a way to increase the GRPC limit? |
@arbesfeld It looks like no for node, at least based on searching around and this thread: https://groups.google.com/d/msg/grpc-io/UiCvZRS1B9I/WvUmc-RfBwAJ. |
Has this been updated to provide an API org option to increase the size? |
We noticed an error today using the BigTable emulator. We were making large
insert
requests against aBigTable
table and it was hanging. When we killed the emulator this message appeared:I read through the documentation and didn't see a mention of a max message size. Is this the case? Any workarounds that you know of for handling large (~10MB) data?
The text was updated successfully, but these errors were encountered: