Conversation
Streaming queries have recently become killable due to context changes. So, a connection could potentially be dead due to a previous query kill. So, we should retry streaming queries also if we get a connection error.
|
Sugu, you accidentally removed the execution bits from Can you please restore it? This is probably the easiest way: # Make sure your branch is clear and you don't have pending changes.
git update-index --chmod=+x test.go
git commitThanks! |
|
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion. go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion, some commit checks broke. go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
|
go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion, some commit checks broke. go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion. go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
|
LGTM |
|
Reviewed 1 of 1 files at r2, 1 of 1 files at r4. Comments from the review on Reviewable.io |
|
Review status: all files reviewed at latest revision, 1 unresolved discussion. go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
|
Review status: all files reviewed at latest revision, all discussions resolved. go/vt/tabletserver/dbconn.go, line 132 [r1] (raw file): Comments from the review on Reviewable.io |
tabletserver: retry streaming query on conn error
|
I think one LGTM is enough. If I understood @enisoc correctly, you could also just merge changes yourself since you're an admin of our repository. |
@erzel
Streaming queries have recently become killable due to context
changes. So, a connection could potentially be dead due to a
previous query kill. So, we should retry streaming queries also
if we get a connection error.