-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
EOF when many steps using same big input artifact #9525
Comments
Have you used PodSpecPatch to increase the resource request? |
@hbrewster-splunk that worked but i think the docs should be updated to mention changing that for init container on steps that use a big input artifact
|
Feel free to submit a PR to improve the docs. |
Hi @terrytangyuan i am new to open source and want to work on this issue . Can you assign it to me |
@2022H1030014G you can raise a PR to fix this even without being assigned |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
@2022H1030014G Are you still working on it? |
If there's no PR, you can just start working on it. |
Signed-off-by: awwwd <[email protected]>
(argoproj#9921) Signed-off-by: awwwd <[email protected]> Signed-off-by: juchao <[email protected]>
i have a 1.2GB artifact on s3
intermittently some of the tasks that use the same artifact as input gets below error:
OR
logs also mention max duration:
another run's 'init' container logs:
its a fan out workflow:
version 3.3.9
The text was updated successfully, but these errors were encountered: