Resetting RavenDB indexes
Blog post from Octopus Deploy
After upgrading an Octopus Deploy server or restoring a database, users might encounter issues such as missing data and errors due to problems with Lucene indexes in the underlying RavenDB document database. Although the data remains intact within RavenDB, it may not appear in the user interface because it is not indexed. To resolve this, users can connect to the RavenDB Management Studio, which is accessible via a specific port on the Octopus server, and reset the indexes by deleting them, prompting automatic rebuilding upon restarting Octopus. This process involves accessing the RavenDB Management Studio with Windows Administrator credentials and restarting both the Octopus service and web portal. If issues persist after these steps, users are advised to contact support for further assistance.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.