-
Notifications
You must be signed in to change notification settings - Fork 580
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
Stress testing for client shutdown in panda proxy client cache #6595
Comments
6 tasks
NyaliaLui
added a commit
to NyaliaLui/redpanda
that referenced
this issue
Oct 20, 2022
This commit also adds options to the RedpandaService for the client cache keep alive and client cache max size configs. Closes redpanda-data#6595
6 tasks
NyaliaLui
added a commit
to NyaliaLui/redpanda
that referenced
this issue
Oct 21, 2022
This commit also adds options to the RedpandaService for the client cache keep alive and client cache max size configs. Closes redpanda-data#6595
NyaliaLui
added a commit
to NyaliaLui/redpanda
that referenced
this issue
Oct 25, 2022
This commit also adds options to the RedpandaService for the client cache keep alive and client cache max size configs. Closes redpanda-data#6595
NyaliaLui
added a commit
to NyaliaLui/redpanda
that referenced
this issue
Oct 28, 2022
The kafka client stop() method is called whenever a client is evicted from the LRU cache. This commit adds a ducktape test that configures the cache to a max size of 1. The test stresses client stop() by issuing many rest requests with two unique users within a 30s loop. The idea is tigger eviction, and consequently client stop(), many times. Closes redpanda-data#6595 This commit also adds options to the RedpandaService for the client cache keep alive and client cache max size configs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When clients are forcefully stopped in the cache we need to make sure that that is safe / good behavior with respect to any on going PP requests that may hold references to the client being stopped.
Originally posted by @dotnwat in #6452 (comment)
The text was updated successfully, but these errors were encountered: