opensearch-project / opensearch-project/data-prepper

Lambda processor should support additional batching option

Open
#6,241 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Is your feature request related to a problem? Please describe.
Current aws lambda thresholds determine when to send the request and if the processor receives a large batch of events from the source, entire batch is split into requests based on the threshold parameters and sent to lambda service asynchronously and then waits for the response. This often results in lambda processor running into connection issues and the pipeline running into memory issues.

Describe the solution you'd like
We need to add another threshold option to limit the number of asynchronous requests and wait for the completion of those requests.

   aws_lambda:
      max_async_requests: <number>

Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the AWS Lambda processor, its existing threshold configuration, and the asynchronous request handling for large batches. Clarify how max_async_requests should limit in-flight requests and when processing should wait for completion. Done means the new option is accepted and enforced, with coverage for large-batch behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
backend, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.