OpenSearch Configuration Change Stuck at 20% and 503 Error Responses

Question

I’m encountering an issue with Amazon OpenSearch Service during a configuration update. The process has stalled at **20%** for over half a day without any progress, with the status message showing "Cluster configuration change in progress."

Additionally, all requests to the domain endpoint return a **503 Service Unavailable** error, making it impossible to proceed with the configuration or access the cluster.

**Key Details:**
- I only checked the box for **“Require HTTPS for all traffic to the domain”** during the configuration change, and thus did **not perform a dry-run**.
- **There are no red indexes** in the cluster.
- The issue is unrelated to HTTP 504 errors.
- Curl command response:
  ```bash
  $ curl "https://vpc-XXXXX.ap-northeast-1.es.amazonaws.com/suggest/question_XXXX/_search?A"
  {
    "message": "No server available to handle the request",
  }
  ```

Could anyone help identify what might be causing this configuration change to get stuck and provide steps to resolve the issue?

Thank you!

Oleksii Bebych · Accepted Answer

Please check this article 
https://repost.aws/knowledge-center/opensearch-domain-stuck-processing

If it does not help, you will have to create a ticket to AWS Technical Support

AM_SS · Answer

Thank you for your response. I referred to the article in the provided URL, but unfortunately, it did not resolve the issue.

In the end, I was able to resolve the issue by creating a new Elasticsearch instance and deleting the instance that was stuck in the processing state.

Thank you for your assistance.

OpenSearch Configuration Change Stuck at 20% and 503 Error Responses

Add your answer

Relevant content