Unfortunately I came across the same problem.
When trying to isolate the problem (having a simple hello world
server-client), the problem seems to go away, i.e server can be shut down.
But when using in my own project, this happens. And despite my effort to
track down the problem, I can't
1. This would depend on the settings that you've configured for keepalive.
Note that this doc is specific to gRPC Core and dependents.
2. Again, for Core and dependents, at present the idle timeout is disabled
by default. GRPC_ARG_CLIENT_IDLE_TIMEOUT_MS is the channel arg to specify
the modify
Hi V R,
Two MB should be fine. Many large production services send individual gRPC
messages in the 1 to 20 MB size range. Above that, I would recommend
chunking the data across multiple messages and the use of streaming RPCs.
-Abhishek
On Mon, Jan 31, 2022, 7:42 AM V R wrote:
> Hello,
> I am
Hello,
I am working with large images and large meshes in medical field and I
need to transfer and serialize those objects directly.
I read here https://developers.google.com/protocol-buffers/docs/techniques that
"Protocol Buffers are not designed to handle large messages. As a general
rule of
