On a related note, seeing this when calling run_func with a large-sized object. Is this a hard limit with RPC?
_MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.RESOURCE_EXHAUSTED
details = "Received message larger than max (239738659 vs. 4194304)"
debug_error_string = "{"created":"@1701456988.779195477","description":"Received message larger than max (239738659 vs. 4194304)","file":"src/core/ext/filters/message_size/message_size_filter.cc","file_line":206,"grpc_status":8}"
at a brief glance that string (Received message larger than max) doesn't appear in DHC or its java dependencies (like grpc-java), i'm currently inclined to blame dhe's envoy config? continuing to look for that magic number 4194304
11:21
4ish mb seems way small for it to be anything that dhe or dhc would restrict to....
colinalworth
11:22 AM
looks like py grpc client default limit
11:22
again, odd in that i expect the py client is already tested for larger tables than 4mb? maybe the flight stuff has different limits so it hasnt come up
On a related note, seeing this when calling run_func with a large-sized object. Is this a hard limit with RPC?
at a brief glance that string (Received message larger than max) doesn't appear in DHC or its java dependencies (like grpc-java), i'm currently inclined to blame dhe's envoy config? continuing to look for that magic number 4194304 11:21 4ish mb seems way small for it to be anything that dhe or dhc would restrict to....
chipkent 11:21 AM Let me know what you find.
colinalworth 11:22 AM looks like py grpc client default limit 11:22 again, odd in that i expect the py client is already tested for larger tables than 4mb? maybe the flight stuff has different limits so it hasnt come up
https://stackoverflow.com/questions/65819952/grpc-not-increasing-max-size-of-the-message-received-message-larger-than-max