Skip to content
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

Remove existing _es090* files since Bloom filters are now deprecated? #10261

Closed
SjonHortensius opened this issue Mar 25, 2015 · 4 comments
Closed

Comments

@SjonHortensius
Copy link

After upgrading to 1.5.0 which includes #8571 I was hoping I could free up some diskspace from our nodes. Is there a way to remove the *_es090 files (since they are unused) now that the functionality is deprecated or do I need to wait for the entire functionality to be removed as well?

@mikemccand
Copy link
Contributor

You cannot [easily] remove these files from existing shards, however natural merging over time will remove them since the newly merged segment will not write any bloom filters.

@SjonHortensius
Copy link
Author

Okay so the only way to get rid of them would be to ex&import existing data to a new index on e/s 1.5 which will then not write the bloom filters? The es090* consumes roughly 40% of our disk-space so this might actually be an interesting option for us

@mikemccand
Copy link
Contributor

Hang on: it's only the .blm files that will go away, and this almost certainly should not be 40% of your index...

@SjonHortensius
Copy link
Author

Ah, you're right; that is actually less then 1%. So maybe this isn't as interesting as I thought. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants