- Newest
- Most votes
- Most comments
Hello,
There could be couple of reasons for this type of error. I would recommend checking the cloudwatch metrics for the domain. Check the cluster health status and storage usage metrics.
Because sometimes if there is no storage space available the OpenSearch cluster's health may degrade, leading to issues with data ingestion, indexing, and query processing. This can cause various services within the cluster to become unresponsive or overloaded.
And if your cluster health is in a red or yellow status, this can also be a possible cause. You can refer this post for fixing the same.
Hi,
In some cases, the OpenSearch Dashboard returns a bad gateway error when a query runs over 120 seconds (as parametrized).
So, you may get such an error on complex queries. Can you try on a simple one (i.e. answering fast for sure) to see if you always get 502? If not, then it mean that you mean have too complex queries or too much data for your current timeout setup.
Best,
Didier
Hello,
check these solutions to resolve your issue
1. Storage and Cluster Health:
- Check CloudWatch metrics: Ensure storage space is sufficient and cluster health is good.
- Action: Add storage or resolve any health issues.
2.Query Timeout:
- Simplify Queries: Run simpler queries to see if the issue persists.
- Adjust Timeout: Increase query timeout settings if needed.
By checking storage, cluster health, and query complexity, you can resolve the "502 Bad Gateway" error.
