[CI] Add resilience when peak loads #22674
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
botelastic
bot
added
needs_team
kuisathaverat
approved these changes
Nov 19, 2020
cachedout
approved these changes
Nov 19, 2020
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
v1v
added a commit
to v1v/beats
that referenced
this pull request
Nov 23, 2020
v1v
added a commit
to v1v/beats
that referenced
this pull request
Nov 23, 2020
v1v
added a commit
that referenced
this pull request
Nov 23, 2020
v1v
added a commit
that referenced
this pull request
Nov 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Avoid as much as possible issues that are caused when the VM provisioner cannot provide such amount of workers concurrently and therefore builds get stuck and get a timeout.
Why is it important?
There were two builds that use the same sha commit, the first build got stuck for 3 hours since apparently there was a peak load, while the second one didn't get stuck.
As long as the provisioner does not scale we need to find ways to mitigate issues with certain adhoc sleeps.
Screenshots
#### Build 1
Build 2
#### Provisioner graphs