1 個回答
- 最新
- 最多得票
- 最多評論
1
OpenSearch throttles by default when the respective threadpool queues are full. High threadpool queues indicate the that the incoming request rate is greater than what the cluster is provisioned to handle.
If you're going beyond this, you would have to setup a feedback mechanism by considering metrics such as CPUUtilization, JVMMemoryPressure, etc. You can set a CloudWatch alarm over the metrics to notify you via SNS as well as configure SNS to invoke a Lambda function to reduce the rate on the client side as required.
已回答 2 年前
相關內容
- 已提問 6 個月前
- 已提問 10 個月前
AWS 官方已更新 2 年前- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
The client might be in another account. The Lambda should execute there and reduce the rate there or should is there a way to to set some rule in OpenSearch to limit and incoming DataStream?