You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current recommended max size on mainnet is 60MB, and most operators manage this using the cli flag --rpc-max-message-size.
Using a response side size limiter doesn't actually protect the node, since it has already done the work to generate the message. Also, the receive limit on the communication with an upstream Execution node has limited value since ENs are currently trusted. This will change, but before that happens, ANs will stop using gRPC to get data from ENs.
Proposed Solution
Update the default max message size to 1GB. This is much higher that current max data sizes and leaves room for state growth, while also putting a reasonable max on the payload sizes.
The text was updated successfully, but these errors were encountered:
4609: [Access] Update default grpc max message size to 1GiB r=peterargue a=peterargue
Closes: #4596
The amount of data returned from some Access API requests has increased over time, resulting in response size errors on Access and Execution nodes. While the max message size is configurable via CLI flags, this PR updates the default to be well above the current largest messages.
Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com>
Problem Definition
Currently, the default grpc max message size used by Access and Execution nodes is 20MB:
flow-go/utils/grpcutils/grpc.go
Line 18 in 6ece1c3
The current recommended max size on mainnet is 60MB, and most operators manage this using the cli flag
--rpc-max-message-size
.Using a response side size limiter doesn't actually protect the node, since it has already done the work to generate the message. Also, the receive limit on the communication with an upstream Execution node has limited value since ENs are currently trusted. This will change, but before that happens, ANs will stop using gRPC to get data from ENs.
Proposed Solution
Update the default max message size to
1GB
. This is much higher that current max data sizes and leaves room for state growth, while also putting a reasonable max on the payload sizes.The text was updated successfully, but these errors were encountered: