-
Notifications
You must be signed in to change notification settings - Fork 871
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
Database inconsistency - Cluster is null error #3825
Comments
Try calling |
I tried that a few times and closed down the console a few times and On Fri, Mar 27, 2015 at 2:27 PM, Luca Garulli notifications@github.com
David Carr |
Could you share the database to debug where 18 comes out? |
Once I removed my java hook from the config file and restarted OrientDB it worked fine. I think the underlying issue/concern is that any Java hook can completely torpedo the OrientDB server and there are no mechanisms to debug what is going on or what runtime problems are occurring. I was able to correlate this new problem to a recently-released java hook but the hook compiled with no errors and the errors only appeared at runtime. |
Do you have any errors to understand what's the problem? |
I'm closing this issue, because is not pertinent anymore. Please feel free to open a new one if you have any other problem with hook management. |
(running server 2.0.5) In the log below, when deleting from cluster 15 I get a server error saying cluster 18 is null but there is no cluster 18 in my schema. This happened to me once before and the only thing I knew how to do is drop database and start over. How can I get the consistency back?
The text was updated successfully, but these errors were encountered: