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년 전2399회 조회
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?

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인