-
Notifications
You must be signed in to change notification settings - Fork 121
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
when graph engine server restart, the connect will be error somtimes #457
Labels
type/question
Type: question about the product
Comments
When graphd server restarted, the old connection will be an invalid connection, and will be keep in NebulaPool. when you getSession and the NebulaPool gives the invalid connection to Session, then you will get the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
error msg:
com.vesoft.nebula.client.graph.exception.IOErrorException: java.net.SocketException: Broken pipe (Write failed)
at com.vesoft.nebula.client.graph.net.SyncConnection.executeWithParameter(SyncConnection.java:192) ~[client-3.0.0.jar!/:?]
at com.vesoft.nebula.client.graph.net.Session.executeWithParameter(Session.java:113) ~[client-3.0.0.jar!/:?]
at com.vesoft.nebula.client.graph.net.Session.execute(Session.java:78) ~[client-3.0.0.jar!/:?]
at com.vesoft.nebula.client.graph.net.SessionWrapper.execute(SessionWrapper.java:32) ~[client-3.0.0.jar!/:?]
The text was updated successfully, but these errors were encountered: