confluentinc / confluentinc/parallel-consumer
Ensure all PC API's are thread safe
Open
blocker
ver:1.0
- Dominant language
- Java
- Stars
- 299
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
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](https://github.com/confluentinc/parallel-consumer/issues/187)
Fixed by:
- #346
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.