Enforce entity by connection limit more strictly #464
Comments
acogoluegnes
added a commit
that referenced
this issue
Dec 1, 2023
In case of too many concurrent creations. References #464
github-actions bot
pushed a commit
that referenced
this issue
Dec 1, 2023
In case of too many concurrent creations. References #464
acogoluegnes
added a commit
that referenced
this issue
Jan 2, 2024
Lock producer and consumer creation in respective coordinator. This adds some contention but should be acceptable as creations are not hot and concurrent operations. Fixes #464
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating producers/consumers at the same time in different threads, the coordinators may not be able to enforce the limit per connection. We then end up with 1 producer/consumer per connection.
One way to mitigate the issue is to create the entities synchronously or to sleep a few milliseconds between multi-threaded creations.
Way to reproduce: set 3 for the limit per connection, loop up to 9, create a consumer with an
Executor. There should be 9 connections for the consumers (tested only with consumers).Note adding too much synchronization can lead to deadlocks on recovery.
The text was updated successfully, but these errors were encountered: