Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop reindexing indexes on new version #12497

Closed
mhajas opened this issue Jun 14, 2022 · 3 comments · Fixed by #15023
Closed

Stop reindexing indexes on new version #12497

mhajas opened this issue Jun 14, 2022 · 3 comments · Fixed by #15023
Assignees
Labels
area/storage Indicates an issue that touches storage (change in data layout or data manipulation)
Milestone

Comments

@mhajas
Copy link
Contributor

mhajas commented Jun 14, 2022

Currently, it is possible to configure Keycloak to reindex caches on startup. Reindexing basically means downtime because while reindexing is in progress, Keycloak is unusable. This can be replaced by a function introduced in Infinispan 14 - udpateIndexSchema this function is faster and makes no changes to index values, so there is no downtime.

@mhajas mhajas added area/storage Indicates an issue that touches storage (change in data layout or data manipulation) team/storage-sig labels Jun 14, 2022
@hmlnarik
Copy link
Contributor

hmlnarik commented Oct 5, 2022

@mhajas Is this duplicate of #12067?

@mhajas
Copy link
Contributor Author

mhajas commented Oct 5, 2022

Nope. Issue #12067 was about investigating how we will be doing no-downtime upgrades of indexes with HotRod. It resulted in scenarios we need to support and what steps we need to handle each scenario in no-downtime way. These scenarios will be added to ISPN testsuite so we are sure new versions don't break it for us. I will do a summary of the steps so we can use it when some changes appear.

Currently, we are not able to do no-downtime upgrades of indexes because we are not able to update the index schema (feature added in ISPN 14). Instead of it, with each startup, we reindex all caches just to make sure we have always the same schema. This reindexing may be time-consuming so we need to get rid of it and it will be done as part of this issue.

@hmlnarik
Copy link
Contributor

Depends on #12494

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage Indicates an issue that touches storage (change in data layout or data manipulation)
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants