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
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:
{"type": "json_logger", "timestamp": "2024-09-16T14:04:13,248Z", "level": "DEBUG", "component": "o.o.i.i.s.f.WaitForForceMergeStep", "cluster.name": "logmanagement2-rec", "node.name": "opensearch-data-os-2", "message": "Force merge still running on [.ds-logs-log-default-000617] with [2] shards containing unmerged segments", "cluster.uuid": "ZbghcuYqTtWRmCHMd4tbyw", "node.id": "cYyrcay5QPS7_zi0HxvyJg" }
How can one reproduce the bug?
Create new Opensearch cluster with hot and warm tiers
Create Index template to allow create datastream index
I think the force_merge setp must be estimate the target size to look if there are sufficious space on node.
And in all case, the setp must be failed because node space left on device instead to failed with Action time out
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: