OpenSearch instance change hangs on copying shards

0

Good morning everybody, I have a test OpenSearch domain running on a t3.medium instance. After creating an index, the cluster status changed on red. To solve, I tried to changes the instance to a superior one, but the dry run told me that was not possible. Hence, I changed it to another t3.medium.

The migration started, but the process is stuck at step 4 of 5, copying the shard 19 of 41. It's been there for 2 days. In the while, I managed to delete the incriminating index, so the cluster status reverted to green. Nevertheless, the migration is still hanging. Any help, please?

Nicorb
已提問 10 個月前檢視次數 598 次
1 個回答
0
已接受的答案

Hi, when the cluster is RED, any blue green deployments that you trigger as a result of configuration changes will get stuck in processing state. Its advised to make sure the cluster is either is green or yellow state before you make any changes to the cluster. Managed Opensearch service performs multiple auto retries (before it gives up) to see if the cluster is out of RED state so that it can finish the Blue Green deployment. Now that the cluster is stuck in processing, there is not much you could do but open a support case for the AWS teams to manually clear the stuck state and continue with blue green deployment.

profile picture
已回答 9 個月前
profile picture
專家
已審閱 7 個月前
  • thank you very much!

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南