Throttling a Client/Index from OpenSearch (ElasticSearch)

0

I have the following setup for logs:

  • Fargate Service -> Firelens/Fluent Bit -> OpenSearch (ElasticSearch) Cluster or
  • Fargate Service -> Cloudwatch -> OpenSearch (ElasticSearch) Cluster

I know about Fluent Bit Throttle, but that is on client side. What would be good mechanism on OpenSearch (ElasticSearch) Cluster side to throttle that Client/Index if he pushes to much data?

Laszlo
質問済み 2年前2401ビュー
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.

AWS
Ajay N
回答済み 2年前
  • 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?

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ