Todd Lipcon has posted comments on this change. ( 
http://gerrit.cloudera.org:8080/9295 )

Change subject: [TestWorkload] an option to retry on read timeouts
......................................................................


Patch Set 3:

I'm not 100% following this. Reads should already have internal retries since 
they're configured to be fault-tolerant, right? so what's the purpose of 
retrying on a read timeout rather than just setting the timeout to be longer so 
that the client's internal retries have a longer budget? Is our issue that our 
internal client doesn't do a good job? Maybe we should fix that, considering we 
rely on this behavior for fault tolerance on long-running queries.


--
To view, visit http://gerrit.cloudera.org:8080/9295
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I54a6b81e4ba3a55676f1fc97cd577a5fe545c550
Gerrit-Change-Number: 9295
Gerrit-PatchSet: 3
Gerrit-Owner: Alexey Serbin <aser...@cloudera.com>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Todd Lipcon <t...@apache.org>
Gerrit-Comment-Date: Tue, 13 Feb 2018 20:33:15 +0000
Gerrit-HasComments: No

Reply via email to