New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File with name config.cd does not exist in storage #10051
Comments
Hi @jamieb22 My best guess is that it was not flushed to the disk. |
Hi @jamieb22 |
Andrey... additional logs shown below.
As far as I know, there is no way to recover from this situation. The above upgrade issue is reproducible. I've seen nearly every time I attempted to an upgrade from 3.1. to 3.2. As an aside: are there any test cases to test the upgrading of Orient DB? As you know, I've highlighted upgrade issues in the past. My experience remains that Orient DB frequently get corrupted when upgrading. Furthermore, once the database gets corrupted, its difficult (and often impossible) for an administrator to recover. It would be nice if Orient DB could repair itself somehow. A missing config.cd file. Can it be regenerated? I still have a server running 2.0.32 because I am too scared to upgrade it.
|
OrientDB Version: 3.2.25
Java Version: 21
OS: Windows
Expected behavior
Have an Orient Db database created by 3.1.7. Upgrade Orient DB to 3.2.25. On DB startup, receive message that the database wasn't closed, and need to run older Orient DB version first. Run 3.1.7 again. Shutdown db. Move to 3.2.25. On startup an error is outputted.
Actual behavior
Steps to reproduce
See above
archiva.zip
<An SQL script to reproduce the problem or a JUnit test case will increase A LOT the chance to have a quick fix>
The text was updated successfully, but these errors were encountered: