-
Notifications
You must be signed in to change notification settings - Fork 870
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
Feature Suggestion: Reusing old RIDs #6450
Comments
Hi. I think that your problem is not reused RIDs, but " lots of disk space usage". Is it correct. If you wish this problem to be fixed please vote on orientechnologies/orientdb-labs#7 . One of its goals "Reuse space which is used to store rid of delete record" . |
Wouldn't it be more efficient to reuse the RIDs? Especially with pagination? |
It leads to the case when you fetch records which are already removed. I sent stale link or have such one in application and all the sudden it appears again , we have received a lot of complaints from users when once made rids reusable. |
Alrighty, I'll go vote on the other thread you linked. |
RIDs are never recycled and this leads to lots of disk space usage.
Perhaps there could be a system index for each cluster with all orphaned RIDs (so OrientDB doesn't have to loop through all records to find if a previous one is empty) and new records would use any available spots, if none are available, create record as per normal.
The text was updated successfully, but these errors were encountered: