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 try to configure an index rollover since a while but so far I got no luck with any of the configurations I tried. I'm aware that the datastream can handle that but I see some disadvantages there and, from my point of view, it should work with regular indices as well.
My goal is to create indices based on the scheme "logstash-${kubernetes.cluster_name}-${$.kubernetes.namespace_name}" and to roll them over once they reach a specific size or document count.
I'm using one default index template with no settings regarding alias, this one is just responsible for setting the primaries and replicas and I got a specific template for the index that actually requires a rollover, see below.
At the moment my indices are created on a weekly bases with the date suffix *-yyyy-wWW
When I run a "GET _plugins/_ism/explain/logstash-cluster1-namespace1-2022-w25" in the DEV API in OpenSearch Dashboard, ILM complains about ""Missing alias or not the write index when rollover [index=logstash-cluster1-namespace1-2022-w25]""
When I do step 3 manually I got this exception:
"cause" : """index name [logstash-cluster1-namespace1-2022-w25] does not match pattern '^.*-\d+$'""",
"message" : "Failed to rollover index [index=logstash-dcek1445stage02-kube-infra-2022-w25]"
OS is missing the suffix 000001 and I did not figure out what configuration I need to apply so the plugin adds this suffix. No matter whether there's a date in the index name or not.
This is how I created the alias manually. Although, this should be handled by the plugin.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi together,
I try to configure an index rollover since a while but so far I got no luck with any of the configurations I tried. I'm aware that the datastream can handle that but I see some disadvantages there and, from my point of view, it should work with regular indices as well.
My goal is to create indices based on the scheme "logstash-${kubernetes.cluster_name}-${$.kubernetes.namespace_name}" and to roll them over once they reach a specific size or document count.
I'm using one default index template with no settings regarding alias, this one is just responsible for setting the primaries and replicas and I got a specific template for the index that actually requires a rollover, see below.
At the moment my indices are created on a weekly bases with the date suffix *-yyyy-wWW
fluentd opensearch configuration:
Simple index template for a specific namespace to add the rollover alias:
rollover policy:
Based on the documentation from OpenSearch: https://opensearch.org/docs/2.0/im-plugin/ism/policies#sample-policy-with-ism-template-for-auto-rollover step 3 and 4 need to be handled by the plugin.
When I run a "GET _plugins/_ism/explain/logstash-cluster1-namespace1-2022-w25" in the DEV API in OpenSearch Dashboard, ILM complains about ""Missing alias or not the write index when rollover [index=logstash-cluster1-namespace1-2022-w25]""
When I do step 3 manually I got this exception:
OS is missing the suffix 000001 and I did not figure out what configuration I need to apply so the plugin adds this suffix. No matter whether there's a date in the index name or not.
This is how I created the alias manually. Although, this should be handled by the plugin.
Have you got any idea how to achieve that?
Also, I'm not sure whether this is a bug or feature request, so I put it into the discussion area.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions