-
Notifications
You must be signed in to change notification settings - Fork 120
[BUG] ISM force_merge on datastream index #1255
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
Comments
I finnaly found a right log on data node that host the last shard without merge segments. |
I think the force_merge setp must be estimate the target size to look if there are sufficious space on node. |
@disaster37 did you try explain API to get the information on the policy failure ? |
The explain api just return timeout, without message that explain the cause of timeout. |
What is the bug?
On Opensearch 2.16.0
I have created ISM policy, with force_merge step to force to have one segment after the datastream index has rolled out and move to warm node. The step always finished on timeout.
After put ISM log level to
DEBUG
, I get the following logs:How can one reproduce the bug?
logs-log-default
Wait Force merge step. The force_merge step always in timeout.
What is the expected behavior?
Force merge run successfully on get one segment per shard.
What is your host/environment?
Opensearch 2.16.0
The text was updated successfully, but these errors were encountered: