-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Add connection read/write timeout #50
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
Comments
I'm having trouble with long-running queries, too, although I couldn't say if MYSQL_OPT_READ_TIMEOUT will solve my problem. I have a long-running SELECT statement that does some amount of CPU-intensive processing for each record. Eventually, the log shows (w/ code from March 2): [MySQL] 2013/04/01 04:02:06 packets.go:62: EOF The duration my SELECT query runs before this happens is variable, so I presume this has something to do with my high CPU load and hitting some kind of timeout with MySQL. Anyway, thanks for the great code. |
According to the documentation, there are four timeouts which can be changed per session. They are: You may be interested in Do you still see the problem when you issue This can also be set by appending |
@jmacd the |
@better0332 do you have a certain issue you try to solve with a read / write timeout or is this more a general question? |
Our network quality is not stable, the client remote connect center mysql server. It seems like trap to driver until |
@better0332 so you solved it by changing OS settings? Is this resolved, then? |
yes, i resolved and I think the read/write timeout may affect connection pool |
We'll close this for now. We can reopen it if @jmacd or somebody else still has problems. |
I raised net_read_timeout and net_write_timeout and it works. On Tue, Apr 30, 2013 at 1:03 AM, Arne Hormann [email protected]:
|
And it will stay closed... Thank you for getting back to us! |
@arnehormann hi ,I got this issue now. The detail like: |
Can we set mysql read/write timeout,?
MYSQL_OPT_READ_TIMEOUT ..
The text was updated successfully, but these errors were encountered: