-
Notifications
You must be signed in to change notification settings - Fork 135
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
.opendistro-ism-config already exists #226
Comments
Hello, can you please include the following:
|
Logs of the terraform/terragrunt of the problem. Again, this is from starting from a fresh AWS ES cluster NOTE: All the [REDACTED] represent ressources. Had to remove the names for professional reasons. Kept the ressources name of the policy for clarity.
Here is the code of the terraform:
|
I encounter this issue when creating multiple (10-30) elasticsearch_opendistro_* resources in the same terraform apply, it seems that whatever resource is being used to generate the unique identifier, it was being called in parallel, and returning the same value to both resources, thus creating a colision. If I encounter this error, doing a second terraform apply will not have a problem. |
It seems like we should treat this as a "back off and retry" error (ie a http 409) instead of a permanent failure. There are a few cases where opendistro/opensearch resources use the wrong error code. |
Hello Everyone, I am facing this issue as well. I am creating Opensearch 2.7 cluster along with 3 ISM policies. Everytime the 2 ISM policies are getting failed with the below error and one of them getting created. |
When creating multiple policy from a fresh AWS OpenSearch cluster, i get this error:
elastic: Error 400 (Bad Request): index [.opendistro-ism-config/4pNn5XhHT3SwvIerntYi-A] already exists [type=resource_already_exists_exception]
From my understanding, the problem comes from the fact that for each policy, the plugins tries to create this index, but only need to create it once. To solve this issue, for now, we need to plan, then apply, then plan and apply again.
It there a workaround for this ? is this a known bug ?
Terraform provider config:
OpenSearch version: 7.10
The text was updated successfully, but these errors were encountered: