-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Functionbeat] Allow to specific the parellization factor for Kinesis. #16901
Labels
candidate
Candidate to be added to the current iteration
enhancement
Functionbeat
good first issue
Indicates a good issue for first-time contributors
Team:Services
(Deprecated) Label for the former Integrations-Services team
Comments
ph
added
Functionbeat
Team:Services
(Deprecated) Label for the former Integrations-Services team
labels
Mar 9, 2020
Pinging @elastic/integrations-services (Team:Services) |
ping @kvch |
andresrc
added
[zube]: Inbox
enhancement
good first issue
Indicates a good issue for first-time contributors
candidate
Candidate to be added to the current iteration
[zube]: Ready
and removed
[zube]: Inbox
labels
Mar 10, 2020
I am currently working on this, will send in a PR soon. The maintainer can assign this to me. |
6 tasks
kvch
pushed a commit
that referenced
this issue
Aug 27, 2020
## What does this PR do? This PR adds the ability to add the parallelization factor configuration to functionbeat when reading from Kinesis streams. https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-parallelization-factor-for-kinesis-and-dynamodb-event-sources/ ## Why is it important? This configuration allows you to process one shard of a Kinesis or DynamoDB data stream with more than one Lambda invocation simultaneously. - Closes #16901
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this issue
Oct 14, 2020
## What does this PR do? This PR adds the ability to add the parallelization factor configuration to functionbeat when reading from Kinesis streams. https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-parallelization-factor-for-kinesis-and-dynamodb-event-sources/ ## Why is it important? This configuration allows you to process one shard of a Kinesis or DynamoDB data stream with more than one Lambda invocation simultaneously. - Closes elastic#16901
kvch
pushed a commit
to kvch/beats
that referenced
this issue
Nov 4, 2020
## What does this PR do? This PR adds the ability to add the parallelization factor configuration to functionbeat when reading from Kinesis streams. https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-parallelization-factor-for-kinesis-and-dynamodb-event-sources/ ## Why is it important? This configuration allows you to process one shard of a Kinesis or DynamoDB data stream with more than one Lambda invocation simultaneously. - Closes elastic#16901 (cherry picked from commit 98c434a)
Merged
6 tasks
kvch
pushed a commit
to kvch/beats
that referenced
this issue
Nov 4, 2020
## What does this PR do? This PR adds the ability to add the parallelization factor configuration to functionbeat when reading from Kinesis streams. https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-parallelization-factor-for-kinesis-and-dynamodb-event-sources/ ## Why is it important? This configuration allows you to process one shard of a Kinesis or DynamoDB data stream with more than one Lambda invocation simultaneously. - Closes elastic#16901 (cherry picked from commit 98c434a)
Merged
6 tasks
kvch
added a commit
that referenced
this issue
Nov 6, 2020
## What does this PR do? This PR adds the ability to add the parallelization factor configuration to functionbeat when reading from Kinesis streams. https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-parallelization-factor-for-kinesis-and-dynamodb-event-sources/ ## Why is it important? This configuration allows you to process one shard of a Kinesis or DynamoDB data stream with more than one Lambda invocation simultaneously. - Closes #16901 (cherry picked from commit 98c434a) Co-authored-by: Ravi Naik <[email protected]>
kvch
added a commit
that referenced
this issue
Nov 6, 2020
## What does this PR do? This PR adds the ability to add the parallelization factor configuration to functionbeat when reading from Kinesis streams. https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-parallelization-factor-for-kinesis-and-dynamodb-event-sources/ ## Why is it important? This configuration allows you to process one shard of a Kinesis or DynamoDB data stream with more than one Lambda invocation simultaneously. - Closes #16901 (cherry picked from commit 98c434a) Co-authored-by: Ravi Naik <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
candidate
Candidate to be added to the current iteration
enhancement
Functionbeat
good first issue
Indicates a good issue for first-time contributors
Team:Services
(Deprecated) Label for the former Integrations-Services team
When you create a function that monitors a Kinesis stream, the way by default that Kinesis operates is to create a lambda per shards. When you have a lot of data this causes the function to lag behind the data.
The solution is to change the parallelization factor and this post. From their documentation:
The text was updated successfully, but these errors were encountered: