Skip to content

Conversation

@JeffreyGroves
Copy link
Contributor

I'm adding directions on how to use the newly installed Redisgears version to upgrade a database. It was a little jarring not having this available on this page. It left me hanging when I needed to upgrade a database. It took me a good five minutes to find the information on how to apply the upgrade to a database. A link to where the rladmin upgrade db... command is explained in our documentation would be good too. I couldn't find one though.

Adding directions on how to use the newly installed redisgears version to upgrade a database. 
It was a little jarring not having this available on this page. It left me hanging when I needed to upgrade a database. It took me a good five minutes to fine the information on how to apply the upgrade to a database.
@dwdougherty
Copy link
Collaborator

The rladmin upgrade ... command is documented here.

Copy link
Collaborator

@rrelledge rrelledge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JeffreyGroves Thank you. I moved the new section up above the uninstall section and made some copy edits.

However, I have a question about the upgrade db commands and examples. My understanding is that the current command examples will upgrade the database to the latest Redis DB version in addition to upgrading the RedisGears version.

Do you think we should change this to provide 2 examples, with and without the Redis DB version upgrade? Or will the user always prefer to upgrade both versions?
Example 1: the current example that upgrades the Redis DB version and the RedisGears version.
Example 2: an example that upgrades the RedisGears version without upgrading the Redis DB version.

@rrelledge rrelledge merged commit 40fc167 into redis:main Jul 9, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants