Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Added docs on how to handle a large response when using FlyteRemote.sync #2932

Merged
merged 17 commits into from
Oct 11, 2022
Merged
4 changes: 4 additions & 0 deletions rsts/community/troubleshoot.rst
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,11 @@ Troubles With Inconsistent Names for Pods and Downstream Resources
- Flyte uses the format ``executionid-node-id-attempt`` from the node to assign a name to a Kubernetes pod or downstream resource.
- But if this is an invalid name for a Kubernetes pod, Flyte assigns a valid name of random characters instead.

Troubles with handling large responses in ``FlyteRemote.sync``
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- ``Received message larger than max (xxx vs. 4194304)`` usually crops up when the message size is too large.
- To fix this, edit the flyte-admin-base-config config map to increase ``maxMessageSizeBytes`` value.
samhita-alla marked this conversation as resolved.
Show resolved Hide resolved


I Still Need Help!
Expand Down