Bump lokistack deployment wait time#920
Open
vyzigold wants to merge 1 commit into
Open
Conversation
The lokistack requires a lot of resources and it seems like we're hitting limits of what our CI is able to handle. It looks like the ingester sometimes flaps between ready and unready state, but eventually gets ready (I haven't seen a must-gather with a lokistack being unready during the must-gather execution). I've seen some lokistacks taking 15 minutes to get ready. Let's raise the wait time to 20 minutes to give CRC enough time to deal with the added load and for lokistack to get ready and settled.
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vyzigold The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The lokistack requires a lot of resources and it seems like we're hitting limits of what our CI is able to handle. It looks like the ingester sometimes flaps between ready and unready state, but eventually gets ready (I haven't seen a must-gather with a lokistack being unready during the must-gather execution). I've seen some lokistacks taking 15 minutes to get ready. Let's raise the wait time to 20 minutes to give CRC enough time to deal with the added load and for lokistack to get ready and settled.