[ https://issues.apache.org/jira/browse/HBASE-15615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238378#comment-15238378 ]
Matt Warhaftig commented on HBASE-15615: ---------------------------------------- [~zghaobac], yes, you and I are completely on the same page. For {quote} "RETRY_BACKOFF\[0\] will never be used" {quote} I had noticed the same thing and also thought that after the first RPC attempt RETRY_BACKOFF[0] should be the backoff factor, not RETRY_BACKOFF[1]. > Wrong sleep time when RegionServerCallable need retry > ----------------------------------------------------- > > Key: HBASE-15615 > URL: https://issues.apache.org/jira/browse/HBASE-15615 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 2.0.0 > Reporter: Guanghao Zhang > Assignee: Guanghao Zhang > Attachments: HBASE-15615.patch > > > In RpcRetryingCallerImpl, it get pause time by expectedSleep = > callable.sleep(pause, tries + 1); And in RegionServerCallable, it get pasue > time by sleep = ConnectionUtils.getPauseTime(pause, tries + 1). So tries will > be bumped up twice. And the pasue time is 3 * hbase.client.pause when tries > is 0. > RETRY_BACKOFF = {1, 2, 3, 5, 10, 20, 40, 100, 100, 100, 100, 200, 200} -- This message was sent by Atlassian JIRA (v6.3.4#6332)