Upgrade Redis to 5.0 #3588
Merged
Upgrade Redis to 5.0 #3588
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
For certain Python 2 dependencies, such as troposphere==2.4.9, the use_2to3 post install instruction does not work with setuptools >= 58. To get around this, we add instruction to downgrade to the latest version of setuptools that does support this. See https://stackoverflow.com/questions/72414481/error-in-anyjson-setup-command-use-2to3-is-invalid
We've been on Redis 2 in production for a long time, and it is being EOL'd. We've been using Redis 5 in development since 5bf37aa in August 2021. Thus, with this experience, we upgrade the live instance to Redis 5 as well. These files are updated for the record, but the actual upgrade was performed via the UI. A full record of actions taken can be seen here: #3576 (comment)
|
Done on production as well:
|
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.
Overview
We've been on Redis 2 in production for a long time, and it is being EOL'd. We've been using Redis 5 in development since https://github.com/WikiWatershed/model-mywatershed/commit/5bf37aadd9c7572fb48947afc1cf8c4a4b125d8c in August 2021. Thus, with this experience, we upgrade the live instance to Redis 5 as well.
These files are updated for the record, but the actual upgrade was performed via the UI. A full record of actions taken can be seen here: #3576 (comment)
This has been done for staging already, and is now being done for production.
Closes #3576