-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Add best_compression back to ILM policy #41274
Comments
Pinging @elastic/es-core-features |
@gwbrown I am new to this project and would like to contribute can I start with this issue? |
Is this issue still active? If yes, I'll take it |
@Vboivin yep, it's still active, let me know if you need any assistance with it. |
I do not think I will be able to do it, it can be taken by someone else |
Any update on adding this feature into ILM policies? It appears this was removed because it requires the index to be closed. Is it possible that this option is available during the shrink portion of the warm phase? Since the data is being copied into a new index I assume this is the opportune time to apply a new compression setting? |
Is the issue still active? |
This issue is still active, we’ve just had other issues that are higher priority. If this feature is important to you, 👍 the issue. Contributions are welcome too! This would probably be an option on the force merge action, as a force merge is required to reformat the data with the higher compression codec. |
@SivagurunathanV so in order to implement this, the step would need to be split into multiple steps (actions) that:
The reason it didn't make sense for the force merge at the time is that since it requires the index to be closed, the data is unavailable while closed, so it should not be something easily done by a user because they may not be aware that it causes data to be unavailable for a time. Hopefully that helps, personally I think this should be a separate step from force merge, but @gwbrown talked about it being an option here, Gordon do you have strong feelings either way? |
I don't have strong feelings about this being an option on the |
This was merged in #49974, so I'm going close this since it's available now, thanks @SivagurunathanV for the PR! |
We originally had the
best_compression
codec option implemented in ILM,however, we removed it at the last minute. We should revisit adding this as an
action in ILM to allow for saving disk space.
Switching to
best_compression
does require the index to be closed, the settingchanged, then a force_merge applied to take advantage of the new codec setting.
That's something we will have to work out in the ILM lifecycle.
The text was updated successfully, but these errors were encountered: