-
Notifications
You must be signed in to change notification settings - Fork 91
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
write: broken pipe #143
Comments
Do you have a sample code of how this is happening? |
first : hi, when i exec cursor.HasMore get the err func SqlHive(ctx context.Context, db *gohive.Connection, result interface{}, sql string) error {
} |
|
How can I avoid such problems |
How is the error happening? Is it a panic inside the call HasMore or similar? Ideally you should be able to check |
It doesn't get panic inside the call HasMore. I have checked cursor.err, at the same time throw: "Write client IP: port-> server IP :port: write: broken pipe". |
So it's not clear to me where you're seeing |
Yes, it should be checked, but I don't know how to check for such problems. |
You could so something like: if cursor.Err.Error() == "Write client IP: port-> server IP :port: write: broken pipe" {
// Recreate the cursor and the connection
} Similar to how the error is check in this test. |
required for each query new conn,close conn at end |
I have a similar problem, is it related to the heartbeat ? |
hi i exec go test to query is ok,but exec main func has error:write: broken pipe
The text was updated successfully, but these errors were encountered: