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
The problem is what if there are a ton of affected indices?
This script will generate the above for all indices.
make sure to adjust the path to commercial/ilm_explain_only_errors.json as this is the source file we are gathering index names from.
for index in $(cat commercial/ilm_explain_only_errors.json | jq -r '.indices | to_entries[] | select((.value.step == "ERROR") and (.value.step_info.reason | contains("no rollover info found"))) | .key' | sort); do
printf 'POST _ilm/move/%s
{
"current_step": {
"phase": "hot",
"action": "rollover",
"name": "ERROR"
},
"next_step": {
"phase": "hot",
"action": "rollover",
"name": "set-indexing-complete"
}
}\n\n' "$index"
done
The text was updated successfully, but these errors were encountered:
In case you run into elastic/elasticsearch#49413, you can manually fix it like this.
The problem is what if there are a ton of affected indices?
This script will generate the above for all indices.
make sure to adjust the path to
commercial/ilm_explain_only_errors.json
as this is the source file we are gathering index names from.The text was updated successfully, but these errors were encountered: