Open ramonsmits opened 1 year ago
A connected issue is that in the documentation about troubleshooting corrupted indexes we link to the RavenDB documentation on how to reset indexes, but that's not relevant for RavenDB 5 because it doesn't expose that option in the studio. That means users will try the suggested option to delete the indexes folder and end up with an audit instance that cannot start.
Describe the bug
Description
All SC instances that use RavenDB 3.5 auto recreated the database including any indexes. This was useful as a user could just stop an instance, delete the folder and start the instance and the database was recreated without issues.
Expected behavior
Same behavior as RavenDB 3.5 instances
Actual behavior
Some database content gets recreated but not the indexes.
Versions
Please list the version of the relevant packages or applications in which the bug exists.
4.30.0
Steps to reproduce
Relevant log output
Additional Information
Workarounds
Users can run the instance setup via:
Possible solutions
Additional information