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
All the metadata of indexes are lost after automatic index rebuilds #7125
Comments
Hi, even if the clause allowLeadingWildcard":true involves only the Query parser behaviour, it is necessary to drop and rebuild the index to re-enable it. |
2 similar comments
Hi, even if the clause allowLeadingWildcard":true involves only the Query parser behaviour, it is necessary to drop and rebuild the index to re-enable it. |
Hi, even if the clause allowLeadingWildcard":true involves only the Query parser behaviour, it is necessary to drop and rebuild the index to re-enable it. |
ok, thx for the confirmation, at least we know now it is a known bug. Which will be resolved very soon...;-) Meanwhile, dropping and recreating these indexes. This lasts for about 1.5hrs per index (20-30M docs per class, multiple indexes per class). Only 17 indexes to go... :-( |
I was not clear. We didn't have knowledge of the bug, but if after a crash the index rebuild procedure doesn't load the metadata, well, the index needs to be rebuilt. So, I'm trying to reproduce the bug, that's not so easy (hammering a running server every time seems to be too much expensive :) ) |
no big deal: one possibility is to launch a virtual server, in that you run ODB server and get it busy; then from the host machine, abruptly stop the virtual server and disable abruptly its access to the disk device. Done. |
I've managed to replicate the bug. |
@robfrank thx! |
…eloads the index metadata refs #7125
FYI, @taburet is working actively on it. |
We are doing final tests, the fix is on SNAPSHOTs and will be part of 2.2.17 |
Our tests are always green. I close and move on 2.2.17 milestone. |
OrientDB Version, operating system, or hardware.
Operating System
Expected behavior and actual behavior
All the metadata of indexes are lost after automatic index rebuilds...
We set the metadata
for all of our Lucene indexes.
After a restart of our server (we had a sudden death of the system), a rebuild was started of nearly all of the indexes, including the Lucene indexes.
Now, I notice that such rebuilt Lucene indexes have not these metadata anymore. Obviously resulting in errors for our queries where we use such wildcards.
The text was updated successfully, but these errors were encountered: