Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Client does not handle streams with more than 100 shards #14

Open
jhecking opened this issue Jul 2, 2021 · 1 comment · May be fixed by #15
Open

Client does not handle streams with more than 100 shards #14

jhecking opened this issue Jul 2, 2021 · 1 comment · May be fixed by #15

Comments

@jhecking
Copy link

jhecking commented Jul 2, 2021

The AWS.DynamoDBStreams.describeStream() function returns max. 100 shards. If the stream consists of more shards than that, the response contains a LastEvaluatedShardId value, which can be passed in a subsequent describeStream() call using the ExclusiveStartShardId parameter, to fetch the remaining shards.

Because the client does not fetch all the shards, it will miss records on very active streams.
@jhecking
Copy link
Author

jhecking commented Jul 2, 2021

Looks like someone else already ran into the same issue as well and addressed it in this commit: zoom-us@aee2f2c. Possible to pull this change and release it in the "official" dynamodb-stream package on npmjs.com?

@jhecking jhecking linked a pull request Jul 2, 2021 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fetch all shards by paginating results Securezapp/node-dynamodb-stream
1 participant
@jhecking