Mike Percy has posted comments on this change.

Change subject: KUDU-2125: Tablet copy client does not retry on failures
......................................................................


Patch Set 10:

(5 comments)

Just one thing I'm wondering about, in the tablet copy client.

http://gerrit.cloudera.org:8080/#/c/8016/10/src/kudu/integration-tests/cluster_itest_util.cc
File src/kudu/integration-tests/cluster_itest_util.cc:

PS10, Line 856: std::remove_if
fancy


PS10, Line 858:  != 
Neat: I didn't know you could check for equality between a thing and an 
optional of a thing.


http://gerrit.cloudera.org:8080/#/c/8016/4/src/kudu/integration-tests/tablet_copy_client_session-itest.cc
File src/kudu/integration-tests/tablet_copy_client_session-itest.cc:

PS4, Line 305: or<thread
> Turns out it was caught because of some existing calls to HasFailure() in e
I'm surprised at this. I've had weird issues trying to do this before and now I 
always use CHECK_OK outside of the main thread. Since the docs claim otherwise, 
do you have any evidence that this is safe to do?


http://gerrit.cloudera.org:8080/#/c/8016/10/src/kudu/tserver/tablet_copy_client.cc
File src/kudu/tserver/tablet_copy_client.cc:

PS10, Line 702: >=
why >= and not == ?


Line 747:       // Polynomial backoff with 50% jitter.
Have you used this before? I plotted y=10x^2 and it seems pretty good -- well 
behaved and no need for a cap.


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

Gerrit-MessageType: comment
Gerrit-Change-Id: I7c8454fc600a841bd15306a2b3b06ddf53130be6
Gerrit-PatchSet: 10
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Dan Burkert <danburk...@apache.org>
Gerrit-Reviewer: Adar Dembo <a...@cloudera.com>
Gerrit-Reviewer: Alexey Serbin <aser...@cloudera.com>
Gerrit-Reviewer: Dan Burkert <danburk...@apache.org>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy <mpe...@apache.org>
Gerrit-Reviewer: Todd Lipcon <t...@apache.org>
Gerrit-HasComments: Yes

Reply via email to