@ancient-wolf-19325 , GET /api/v1/data/node_executions/kaas/development/absnql4wjdcsn2g89qxw/n1-0-n2 api failed with error below: grpc: received message larger than max (48208327 vs . 4194304). Do we need to increase grpc msg size limit ? if so how can do it ?

Yes, you need to increase the gRPC message size limit. This error occurs when the message size exceeds the default gRPC limit of 4MB. You can adjust this limit in the Flyte configuration. To increase the gRPC message size limit, modify the

maxMessageSizeBytes

setting in the FlyteAdmin configuration. According to Flyte documentation, you can set this value higher in the

flyte-admin-base-config

config map. Use the command

kubectl edit cm flyte-admin-base-config -n flyte

to update the configuration. Would you like more detailed instructions on how to perform this configuration change? Sources: - Flyte documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325, Under flyte-admin-base-config, server.yaml added below lines but didnt worked grpc: maxMessageSizeBytes: 100000000

Ensure that the configuration is correctly applied and that the FlyteAdmin service is restarted to reflect the changes. Verify that the

maxMessageSizeBytes

setting is correctly placed under the

server

section in the

flyte-admin-base-config

config map. Use

kubectl describe cm flyte-admin-base-config -n flyte

to check if the changes are applied. Would you like more detailed steps on verifying and applying the configuration? Sources: - https://discuss.flyte.org/t/16668285/dear-flyte-community-we-are-experiencing-a-cache-put-failure/ - https://discuss.flyte.org/t/2423924/hi-i-m-trying-to-sync-an-execution-using-flyteremote-sync-bu/ 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@victorious-jelly-28729 If I remember correctly you're using flyte-binary? If that's the case, it should go on your values file as

configuration:
  inline:
    server:
      maxMessageSizeBytes:

@average-finland-92144, we are using flyte-core, maxMessageSizeBytes changes worked