-
Notifications
You must be signed in to change notification settings - Fork 977
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
Stmt_Cached grow beyond mysql-max_stmts_cache causing ProxySQL to crash #1198
Comments
Issue confirmed |
In 1.4 the handling of prepared statements were rewritten to solve some design limitations. The code responsible for `Stmt_Cached` and `Stmt_Max_Stmt_id` wasn't migrated tho. Fixed now.
In 1.4 the handling of prepared statements were rewritten to solve some design limitations.
|
Fixed in current branch 1.4.4 |
Hi Rene
Anything we can do to clear the cache on prepared statements before the
server runs out of memory ?
When do you expect to release 1.4.4 ?
Thanks for your support!
Best regards
Klaus Overgaard
Den 6. okt. 2017 23.58 skrev "René Cannaò" <[email protected]>:
Fixed in current branch 1.4.4
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1198 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AfByLLZJSwp04oLmptwpMxsec26g2ZnCks5spqJqgaJpZM4PunwC>
.
|
Hi @renecannao This fix is not ported to 2.x, also the mysql-max_stmts_cache documentation is missing from |
We are using ProxySQL 1.4.1. The caching of Prepare statements seems to grow infinitely. Our mysql-max_stmts_cache is set to default 10.000, but Stmt_Cached and Stmt_Max_Stmt_id grow way beyond until all server memory is consumed (12 GB) and eventually ProxySQL crash.
Here is a screnshot of the memory consumption. The busier our servers are, the quicker the stmt cache grows: https://gyazo.com/358232ad78361532eb2131ba2e21c73c
The text was updated successfully, but these errors were encountered: