Reduce pressure on Elasticsearch in staging env #379
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
As discussed, the previous config seems to lead to indexing failures in the staging environment due to Elasticsearch tripping memory-related circuit breakers and/or timing out.
yrodiere
force-pushed
the
no-staging-overload
branch
from
8ac26e4 to
8201b69
Compare
|
I thought we've already applied the change; but now I see:
Those auto-merge PRs are getting stuck as some other PR gets merged 🙈 😖 |
Yep, it only merges if it can be fast-forwarded I think. |
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.
As discussed, the previous config seems to lead to indexing failures in the staging environment due to Elasticsearch tripping memory-related circuit breakers and/or timing out.