Filter out pending stages from killed builds in queue endpoint #2653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Those pending stages are caused by cancelling a multi-pipeline job while not all stages are started yet. Then the later stages are still in a pending state. This causes trouble with the autoscaler because the autoscaler uses those pending stages to determine the backpressure and starts workers.
Another approach would be to properly kill those pending stages, but my Golang skills are currently too limited to accomplish this. Also further debugging would be needed to determine why it didn't worked in the first place. So this failsafe here is a good additional step to avoid unneeded upscale of agents.
The table looks like this right now:
Full table with pending stages with a query before and after this change