Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
There are currently tests to run a high amount of connects and disconnects, but there are no tests that create and maintain connections to bring Kafka to its limit.
My plan is to write a test that will take a desired number of clients (KafkaConsumer, KafkaProducer, and AdminClient), the keep-alive rate for these connections, and the number of threads desired to maintain these connections.
Each worker will spawn the desired number of threads that will find connections that need to be maintained and act on them.
Attachments
Issue Links
- links to