bigtable: Use correct value for message size
Fixes #1242
Change-Id: Ifa19d44ab79b29481023c0e4ca997e36b6693c93
Reviewed-on: https://code-review.googlesource.com/c/36171
Reviewed-by: Jean de Klerk <deklerk@google.com>
Reviewed-by: Solomon Duskis <sduskis@google.com>
Reviewed-by: kokoro <noreply+kokoro@google.com>
diff --git a/bigtable/bigtable.go b/bigtable/bigtable.go
index 07b4ee8..28c0c92 100644
--- a/bigtable/bigtable.go
+++ b/bigtable/bigtable.go
@@ -71,7 +71,7 @@
o = append(o,
option.WithGRPCConnectionPool(4),
// Set the max size to correspond to server-side limits.
- option.WithGRPCDialOption(grpc.WithDefaultCallOptions(grpc.MaxCallSendMsgSize(100<<20), grpc.MaxCallRecvMsgSize(100<<20))),
+ option.WithGRPCDialOption(grpc.WithDefaultCallOptions(grpc.MaxCallSendMsgSize(1<<28), grpc.MaxCallRecvMsgSize(1<<28))),
// TODO(grpc/grpc-go#1388) using connection pool without WithBlock
// can cause RPCs to fail randomly. We can delete this after the issue is fixed.
option.WithGRPCDialOption(grpc.WithBlock()))
