-
Notifications
You must be signed in to change notification settings - Fork 8
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
Jobs stuck in PENDING
because StartExecutionManager
invokes worker with too large payload
#1689
Comments
Submitted 3 jobs to |
The manager Lambda in |
Same for |
We will want to continue to monitoring to ensure that number of pending jobs is approaching 0, and that jobs are succeeding. |
Looking at the Step Function console in Looking at the The number of pending jobs will take awhile to decrease substantially, because the Batch job has to start running before the job status changes. |
The last release #1685 introduced a bug causing jobs to get stuck in
PENDING
. I have only diagnosed the problem in the following two deployments, so not sure if it's affecting any of the others:hyp3-pdc
: 10,000 jobs inPENDING
hyp3-edc-prod
: 9,210 jobs inPENDING
From the most recent log stream for
StartExecutionManager
inhyp3-pdc
:Most recent log stream for
hyp3-edc-prod
shows the same error.Per @asjohnston-asf:
For context, see #1676 and #1272
The text was updated successfully, but these errors were encountered: