Open earshinov opened 4 years ago
Is it something that could possibly be fixed by upgrading to 3.0.32?
Hi @earshinov . OSystem database is not critical, you can delete it. But in general, the problem is caused by the fact that you use V1 version of cluster. You should use V2 version of cluster, which is durable. If your database is not big, you can export to JSNO and then import it and you will perform the migration. In future, we are planning to implement automatic migration between versions.
Hi @earshinov , did removal of system database resolve your issue?
@laa , Yes, rm -rf databases/OSystem/
helped, thanks! I will try migrating to cluster V2 a bit later.
@laa , Can you please point me to the documentation on cluster versions (v1 vs v2)? I must be missing something: as far as I understand, in the test setup I am tinkering with at the moment I shouldn't be using OrientDB in distributed mode at all because I only have a single server.
@earshinov by cluster I mean storage cluster, disk-based cluster, like a table, not distributed cluster.
@laa , Could you give me a hint about how to switch between cluster v1 and v2?
One of the reasons why I'm asking is that I recreated the database recently. Given that OrientDB used cluster v1 when recreating the database (apparently), why would it switch to cluster v2 when I export and import the database?
I'm still trying to glean some information on cluster v1 and v2. Is cluster v2 something that appeared between 3.0.30 and 3.0.33? I didn't use older versions of OrientDB. I can't find any information about cluster v2 on the OrientDB 3.0 Release Notes page.
Hi @earshinov if I remember correctly I have already answered your question. Have not I?
@laa, We didn't experience this issue any more, and also after migrating to OrientDB 3.1.3 we have storage.cluster.version = 2
in global configuration (studio/index.html#/dashboard/general). I guess, everything should be fine and this ticket can be closed, at least for now.
OrientDB Version: 3.0.31
Java Version:
OS:
Expected behavior
No exceptions on startup.
Actual behavior
Steps to reproduce
None, but maybe you have come clues?