时间戳

首页 > 解决方案 > AWS elastic search cluster becoming unresponsive

aws-elasticsearch - AWS elastic search cluster becoming unresponsive

问题描述

we have several AWS elastic search domains which sometimes become unresponsive for no apparent reason. The ES endpoint as well as Kibana return bad gateway errors after a few minutes of trying to load the resources.

The node status message is the following (not that it's any help): /_cluster/health: {"code":"ProxyRequestServiceException","message":"Unable to execute HTTP request: Read timed out (Service: null; Status Code: 0; Error Code: null; Request ID: null)"}

Error logs are activated for the cluster but do not show anything relevant for the time at which the cluster became inactive.

I would like to at least be able to restart the cluster but the status remains "processing" seemingly forever.

标签： aws-elasticsearch

解决方案

不幸的是，如果您使用的是 AWS ElasticSearch 服务（因为不是在您自己的 EC2 实例上构建它），许多...嗯...大多数...管理 API 和功能都受到限制，因此您无法深入研究如果你从头开始构建它，你就可以做到。

我发现 AWS Support 在需要时可以很好地了解事情的真相，所以我建议您开一张支持票。

我希望不是这样，但是使用他们的服务既好又容易（因为您不必自己构建和维护基础设施），但是从管理员或故障排除的角度来看，您会失去很多功能。:(

推荐阅读