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
What is the bug?
I one of my Opensearch Clusters I have 21 policies but the GET _plugins/_ism/policies counts 21 policies and only returns 20 policies. It omits one specific policy with the name shrink_delete. I can get, update, delete and recreate the policy. I can also use it but it wont show up in the reponse of the API get request. It seems like it is cached some where causing this issue.
Even deleting the .opendistro-ism-config and recreating all policies did not help.
A full cluster restart did not help. What I found odd, is the fact that the opensearch dashboard returns the policy when calling https://your-dashobard.exampley/api/ism/policies?from=0&size=100&search=&sortField=id&sortDirection=desc.
This issues i causing my custom tool to fail, as it does not expect the shrink_delete policy to exist and therefore does not habe a seq_no and primary_term.
How can one reproduce the bug?
I don't think there is a way to reproduce it in a simple way.
What is the expected behavior?
I would expect that 21 policies are getting returned.
What is the bug?
I one of my Opensearch Clusters I have 21 policies but the
GET _plugins/_ism/policies
counts 21 policies and only returns 20 policies. It omits one specific policy with the nameshrink_delete
. I can get, update, delete and recreate the policy. I can also use it but it wont show up in the reponse of the API get request. It seems like it is cached some where causing this issue.Even deleting the
.opendistro-ism-config
and recreating all policies did not help.A full cluster restart did not help. What I found odd, is the fact that the opensearch dashboard returns the policy when calling
https://your-dashobard.exampley/api/ism/policies?from=0&size=100&search=&sortField=id&sortDirection=desc
.This issues i causing my custom tool to fail, as it does not expect the
shrink_delete
policy to exist and therefore does not habe a seq_no and primary_term.How can one reproduce the bug?
I don't think there is a way to reproduce it in a simple way.
What is the expected behavior?
I would expect that 21 policies are getting returned.
What is your host/environment?
Do you have any screenshots?
The text was updated successfully, but these errors were encountered: