Index locking is still required for ServiceControl 6.20.0 to 6.21.0 - #8521
Open
mauroservienti wants to merge 1 commit into
Open
mauroservienti wants to merge 1 commit into
mauroservienti wants to merge 1 commit into
Conversation
Versions 6.20.0 and 6.21.0 still reset a migrated index to the database default (Corax) at start-up when it is not locked. The fix ships in 6.21.1. Also document how to recover from an index that was reset to Corax after being unlocked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
#8496 stated that locking a migrated index is not required starting with ServiceControl 6.20.0. That is not the case: 6.20.0 and 6.21.0 still deploy their index definitions without the search engine configured on the index, so RavenDB builds a side-by-side
ReplacementOf/<index>that falls back to the database default, which is Corax for databases created before 6.20. A customer hit this after unlocking a migratedMessagesViewIndexWithFullTextSearch.The fix, keeping the search engine configured on an index when ServiceControl deploys its index definitions, is planned for ServiceControl 6.21.1: Particular/ServiceControl#5946.
Changes to
servicecontrol/ravendb/search-engine.md:Note
This should be merged once ServiceControl 6.21.1 is released, or the version references adjusted if the fix ships in a different version.
🤖 Generated with Claude Code