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

Ensure all PC API's are thread safe #186

Open
Tracked by #172
fowlerp-qlik opened this issue Feb 2, 2022 · 0 comments
Open
Tracked by #172

Ensure all PC API's are thread safe #186

fowlerp-qlik opened this issue Feb 2, 2022 · 0 comments
Assignees
@astubbs
Labels
blocker Blocker issue ver:1.0

Comments

@fowlerp-qlik
Copy link

fowlerp-qlik commented Feb 2, 2022 •
edited by astubbs
Loading

Currently PC is multi threaded but underlying Kafka consumer is not. So a scenario such as

  1. thread one subscribes to topic one
  2. thread two subscribes to topic two

will fail since the underlying kafka consumer will reject the second subscribe, due to the consumer's thread safety checks

Relates to: Enable changing of topic subscription before or after PC has started #187

Fixed by:
This was referenced Feb 2, 2022
Open
Closed
@astubbs astubbs changed the title Provide complete Parallel consumer multithreading Ensure all PC API's are thread safe Feb 3, 2022
@astubbs astubbs self-assigned this Feb 3, 2022
@astubbs astubbs added blocker Blocker issue ver:1.0 labels Feb 3, 2022
@astubbs astubbs mentioned this issue Jul 12, 2022
Closed
2 tasks
@astubbs astubbs linked a pull request Jul 12, 2022 that will close this issue
feature #520: Thread safe User API exposure of ALL Consumer APIs #346
Closed
2 tasks
@astubbs astubbs removed a link to a pull request Aug 17, 2022
feature #520: Thread safe User API exposure of ALL Consumer APIs #346
Closed
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@astubbs astubbs

Labels
blocker Blocker issue ver:1.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@astubbs @fowlerp-qlik