This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
Revert "Upgrade elasticsearch for logs on integration" #4842
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
|
👍 😞 This is a good indication of how creaking and old our logging infrastructure is and how badly it needs to be replaced. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reverts #4840
We did the upgrade which went smoothly, but the redis river stoppped consuming data from redis and it's not clear how to fix it, so we're downgrading for now. We may have to use a different redis river plugin, or, as rivers are deprecated change our approach entirely.
Note that downgrading may mean we can no longer read the indexes but as it's integration we'll be able to delete all the data and start again.