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

maxNumberOrWorkers in @KinesisListener is ignored #181

Open

Irteza-S opened this issue Sep 7, 2023 · 0 comments

Contributor

Irteza-S commented Sep 7, 2023

The field maxNumberOrWorkers is being ignored when using the @KinesisListener

How we tested :

have running 1 MN app with a KinesisListener configured with maxNumberOrWorkers = 3
have a KinesisStream with 6 shard

What will happen :

in the log we can see that the listener is consuming the 6 shards instead of 3
in the dynamo db record we can also see that each shard is linked to the unique listener

What is expected :

the listener does only consume a maximum of maxNumberOrWorkers shards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment