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.

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

Implement a pool of topic-partition workers #347

Open
k32 opened this issue Sep 26, 2019 · 3 comments
Open

Implement a pool of topic-partition workers #347

k32 opened this issue Sep 26, 2019 · 3 comments

Comments

@k32
Copy link

k32 commented Sep 26, 2019

group_subscriber_v2 behavior adds parallelism to group subscribers. However, spawning too many parallel workers may become a problem. There should be a way to put an upper limit on the number of parallel workers.

@k32 k32 changed the title Implement a worker pool for topic-partition workers Implement a pool of topic-partition workers Sep 26, 2019
@k32 k32 mentioned this issue Oct 4, 2019
@jeffrade
Copy link

However, spawning too many parallel workers may become a problem.

Would having 6 partitions cause disruption? How many is too many? I'm seeing connection issues to Confluent.

@k32
Copy link
Author

k32 commented Nov 11, 2019

Hi!

How many is too many?

It depends on the broker settings. We don't use Confluent-managed Kafka, so I don't know how many parallel connections per host they allow. In relative terms 6 doesn't seem too many, we easily use 20 per host.

@jeffrade
Copy link

@k32 Thanks, appreciate the quick response.

Any idea(s) what might be causing our issue here: #357

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants