Skip to content
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.

Sign up for GitHub

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

Jump to bottom

sql: RPC error leaks through the client connection #4709

Closed
knz opened this issue Feb 28, 2016 · 3 comments
Closed

sql: RPC error leaks through the client connection #4709

knz opened this issue Feb 28, 2016 · 3 comments
Labels
C-investigation Further steps needed to qualify. C-label will change. help wanted Help is requested / needed by the one who filed the issue to fix it.
Milestone
1.0

Comments

@knz
Copy link
Contributor

knz commented Feb 28, 2016

Found in this Jepsen test result: http://52.91.194.28/cgi-bin/display.py?entry=20160228T231618

The following error is reported via the SQL connection to the client:

ERROR: failed to send RPC: too many errors encountered (1 of 1 total): read tcp 172.31.57.101:57560->172.31.53.252:26257: use of closed network connection

Question 1: is it OK that such an error (generated in roachpb/errorgs.go / kv/send.go) can arrive to the client?

Question 2: what scenario explains how this error was generated?
@knz knz added help wanted Help is requested / needed by the one who filed the issue to fix it. C-investigation Further steps needed to qualify. C-label will change. labels Feb 28, 2016
@knz
Copy link
Contributor Author

knz commented Feb 28, 2016

Another instance: http://52.91.194.28/cgi-bin/display.py?entry=20160228T233701

@petermattis petermattis added this to the 1.0 milestone Feb 29, 2016
@knz
Copy link
Contributor Author

knz commented Feb 29, 2016

( #4036 )

@knz
Copy link
Contributor Author

knz commented Sep 4, 2016

Dup of #4421

@knz knz closed this as completed Sep 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-investigation Further steps needed to qualify. C-label will change. help wanted Help is requested / needed by the one who filed the issue to fix it.
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
2 participants
@knz @petermattis