After system restart, OrientDB fails to start #10250
Comments
suneelkumarch
changed the title
|
I'm also occasionally encountering a similar NullPointerException in ODurablePage (using version 3.2.32). Here are a few example stacktraces: Another: |
|
Hi, This looks some issues in the storage logic, I do remember that some fixes in the storage logic have been done in some early releases of 3.2.x so I do suggest to update to the last hotfix, also it seems that the issues are mostly around the OSystem database, that if you are not using some advanced features like auditing can be removed safely and it will be recreated, let me know if you still have problem with the newer version of the OrientDB |
|
@tglman if the observation is just with System DB(OSystem), the deleting it and restarting orientdb service recreates the system DB. However, in my case this issue is observed with not just with system DB (OSystem), but also with application DB as well.. |
|
Thank you for the comments! A few more details/questions:
Thanks again! |
|
Hi, Are you using volumes for the data folder in your k8s deploy ? Regards |
|
Thanks, @tglman. I can't speak for the original reporter, but in my case, I'm not using K8s at all. So no volumes for the data folder. Just running OrientDb locally on a Windows PC with only local access. |
|
@tglman Yes, in my case, I am using k8s volumes. |
@tglman using k8s volumes has any observations with orientdb, is it? |
|
Hi @suneelkumarch, We do suggest to use volumes, because containers filesystems are not designed for databases, so if you are using volumes you are doing the right way. I was double checking this, if you are using volumes this errors should come from some other places, did you have this issues after an upgrade or you get this errors also when using the database with the exact same version of OrientDB of which it was created ? |
|
Hi @tglman, we get there errors on the same version of the orientdb, NO upgrades were performed. This observation is seen after the system was restarted(not a graceful shutdown), where orientdb is running as Pod. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OrientDB Version: 3.2.18
OS: docker image
Expected behavior
OrientDB is deployed to as container in K8s cluster.
OrientDB runs during the normal operation.
On a node/cluster restarted, its expects that orientdb starts and works as expected.
Actual behavior
At times OrientDB fails to start and ends-up in CrashloopBackOff, with the folllowing error
Exception
<ID>in storageplocal:/orientdb/databases/OSystem: 3.2.18 (build 7589013, branch UNKNOWN) [OLocalPaginatedStorage]`Complete StackTrace:
The text was updated successfully, but these errors were encountered: