You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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
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?
The text was updated successfully, but these errors were encountered: