Skip to content

Recommend migrating existing ServiceControl databases from Corax to Lucene - #8500

Merged
ramonsmits merged 1 commit into
masterfrom
servicecontrol-lucene-migration-recommended
Sep 18, 2026
Merged

ramonsmits merged 1 commit into
masterfrom
servicecontrol-lucene-migration-recommended

Conversation

@ramonsmits

Copy link
Copy Markdown
Member

Aligns the RavenDB search engine page, the 6.19 to 6.20 upgrade guide, and the troubleshooting guide with the 6.20.0 release notes: migrating existing databases to Lucene is recommended, with symptoms that indicate urgency and an explanation of why Lucene fits the ServiceControl workload.

… Lucene

The 6.20 search engine page and 6.19 to 6.20 upgrade guide read as if
migrating to Lucene is optional. Align them with the 6.20.0 release
notes: migration is recommended for all existing error and audit
instances, with symptoms that indicate urgency. Add a troubleshooting
section for the search engine custom check and point the stale index,
high CPU, and dirty memory sections at the Lucene migration.
@ramonsmits
ramonsmits marked this pull request as ready for review September 17, 2026 10:25
@ramonsmits
ramonsmits merged commit b64f1b2 into master Sep 18, 2026
4 checks passed
@ramonsmits
ramonsmits deleted the servicecontrol-lucene-migration-recommended branch September 18, 2026 10:32
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