-
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
100% CPU usage if admin port is not free while ProxySQL is started #895
Comments
Hi Can, Thank you for the report. I will look further into it. |
renecannao
added a commit
that referenced
this issue
Feb 16, 2017
Error |
renecannao
added a commit
that referenced
this issue
Feb 16, 2017
Fixed in 1.3.4 (soon to be released) and 1.4.0 |
minichate
pushed a commit
to minichate/proxysql
that referenced
this issue
Mar 6, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
ProxySQL version: 1.3.3-0-gf2b677a and 1.3.2-1-gd71a745
on CentOS 7
If the admin port (default 6032) is used by another process, ProxySQL seems to use 100% cpu after startup. Also if the port becomes free afterwards, it doesn't recover.
You can reproduce it easily by using netcat or something similar. Using netcat, bind to port 6032;
Then on another shell start ProxySQL. You should see ProxySQL consuming 100% cpu.
Maybe we're polling for the socket to become free too often? If I strace the process, lots and lots of these show up:
I've checked fd=37 and that's proxysql_admin.sock, I believe fd=35 is the tcp socket. I can't find that inode in the tcp connections though.
Thanks! :)
The text was updated successfully, but these errors were encountered: