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.

Sign up for GitHub

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

Update control_plane.rst doc #1229

Merged
merged 2 commits into from
Oct 7, 2022
+1 −3
Merged

Update control_plane.rst doc #1229

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
defc92b
Update control_plane.rst
Ln11211 Oct 7, 2022
8e4e2f4
Update control_plane.rst
Ln11211 Oct 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/source/design/control_plane.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,9 +301,7 @@ You can use :meth:`~flytekit.remote.remote.FlyteRemote.sync` to sync the entity

.. note::

During the sync, you may come across ``Received message larger than max (xxx vs. 4194304)`` error if the message size is too large. In that case, edit the ``flyte-admin-base-config`` config map using the command ``kubectl edit cm flyte-admin-base-config -n flyte`` to increase the ``maxMessageSizeBytes`` value. Refer to the :ref:`flyte: <troubleshoot>` in case you've queries about the command's usage.

- To fix this error, edit the flyte-admin-base-config config map to increase ``maxMessageSizeBytes`` value.
During the sync, you may come across ``Received message larger than max (xxx vs. 4194304)`` error if the message size is too large. In that case, edit the ``flyte-admin-base-config`` config map using the command ``kubectl edit cm flyte-admin-base-config -n flyte`` to increase the ``maxMessageSizeBytes`` value. Refer to the :ref:`troubleshooting guide <troubleshoot>` in case you've queries about the command's usage.

``node_executions`` will fetch all the underlying node executions recursively.

Expand Down