Index locking is still required for ServiceControl 6.20.0 to 6.21.0 - #8521
Open
mauroservienti wants to merge 4 commits into
Open
mauroservienti wants to merge 4 commits into
mauroservienti wants to merge 4 commits 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>
… the audit index rebuild in the 6.20 upgrade guide
…earch engine docs - Fix anchor links to numbered headings, the docs engine drops the step number - On 6.20.0 and 6.21.0 a rebuilt index uses the database search engine, not the one of the existing index - Delete the Corax replacement before locking the migrated index, and restart RavenDB on Windows in between: while the index is locked the delete can have no effect, and RavenDB can keep files of a deleted replacement open - Give the already-swapped case a path for 6.20.0 and 6.21.0 as well - Move the recovery steps out of the migration procedure into their own section and state once that the lock is not necessary from 6.21.1 - Document that from 6.21.1 new indexes in existing databases use Lucene Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mauroservienti
force-pushed
the
servicecontrol-lock-index-until-6.21.1
branch
from
October 5, 2026 11:24
a98de8f to
22019f3
Compare
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
2 participants
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 said that a lock on a migrated index is not necessary from ServiceControl 6.20.0. That is not correct. Versions 6.20.0 and 6.21.0 deploy their index definitions without the search engine configured on the index. RavenDB then builds a side-by-side
ReplacementOf/<index>with the database default. For databases created before 6.20, the default is Corax. A customer unlocked a migratedMessagesViewIndexWithFullTextSearchand the index was reset to Corax.The fix is planned for ServiceControl 6.21.1: Particular/ServiceControl#5946. ServiceControl then keeps the search engine configured on an index when it deploys its index definitions.
Changes to
servicecontrol/ravendb/search-engine.md:Changes to
servicecontrol/upgrades/6.19to6.20.md:MessagesViewIndexin 6.20 (Remove decommissioned endpoints from usage reports ServiceControl#5670). It explains the one-time rebuild and the steps for a locked, migrated index.Note
Merge this after the release of ServiceControl 6.21.1. If the fix ships in a different version, change the version references first.