-
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
Index is screw up #4089
Comments
Having a similar problem with 2.1-rc2 here. When orientdb is trying to rebuild the database via WAL I get following exception:
It's not only occuring with an upgrade form an older version it also happens when I just kill the process and so the WAL is used on next startup. |
Sorry I do not get it. You killed the server and trying to update db ? |
The initial poster said its happening on an upgrade from 2.0.8 to 2.1-rc2 but I can also reproduce it with a fresh 2.1-rc2 database with some indices. When you forcefully stop the database (e.g. killing the process) the WAL is used on next startup and when it tries to rebuild the indices on that startup the error occured for me. |
We support binary compatibility if you do not kill db process but correctly close it. |
you can download db at this link |
any update? |
have seen same issue on (2-1.SNAPSHOT). "We support binary compatibility if you do not kill db process but correctly close it." |
we don't have this issue before 2.1 version. |
@machak if you crash server then you should restart it and then close it again. So your data will not be corrupted. |
Fixed, coul dyou try now ? |
With 2.1-rc3 it works now for me :) |
yes. it work now |
May be related... I'm seeing the following trace when querying the graph db using the JAVA API
First occurred in 2.1.2. I tried upgrading to 2.1.7 but the issue remained. I have done both proper restarts and shutdowns of the orientdb server and have tried to rebuild all indexes but no luck. Possible regression? |
Hi Daniel, вт, 8 Дек 2015, 20:18, Daniel Lawry notifications@github.com:
twitter:@Andrey_Lomakin linkedin:https://ua.linkedin.com/in/andreylomakin |
it try to screw up my index when i migrated from 2.0.8 to 2.1-rc2.
FYI. indexes are exist for 2.0.8 but it's rebuild and deleted at 2.1-rc2 due to following issue. any idea? this issue will only affect for hash index only. furtheremore, the save button is disabled when create index at studio.
2015-05-06 11:32:55:455 WARNING {db=sport} Cannot load index 'account.language' from storage (rid=#1:1012): rebuilt it from scratch [OIndexNotUnique]{db=sport} Cannot rebuild index 'account.language' from storage (rid=#1:1012) because 'java.lang.IllegalArgumentException: File with id 3560 not found in WOW Cache'. The index will be removed in configuration
com.orientechnologies.orient.core.exception.OStorageException: File with name account.language.hib does not exist in storage sport
The text was updated successfully, but these errors were encountered: