You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/07/07 02:54:11 UTC
[jira] [Comment Edited] (HBASE-16172) Unify the retry logic in
ScannerCallableWithReplicas and RpcRetryingCallerWithReadReplicas
[ https://issues.apache.org/jira/browse/HBASE-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365513#comment-15365513 ]
Ted Yu edited comment on HBASE-16172 at 7/7/16 2:53 AM:
--------------------------------------------------------
Failed test (TestReplicationSmallTests) was caused by HBASE-16087
It is tracked in HBASE-16185
was (Author: yuzhihong@gmail.com):
Failed test was caused by HBASE-16087
It is tracked in HBASE-16185
> Unify the retry logic in ScannerCallableWithReplicas and RpcRetryingCallerWithReadReplicas
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-16172
> URL: https://issues.apache.org/jira/browse/HBASE-16172
> Project: HBase
> Issue Type: Bug
> Reporter: Yu Li
> Assignee: Ted Yu
> Attachments: 16172.v1.txt, 16172.v2.txt, 16172.v2.txt
>
>
> The issue is pointed out by [~devaraj] in HBASE-16132 (Thanks D.D.), that in {{RpcRetryingCallerWithReadReplicas#call}} we will call {{ResultBoundedCompletionService#take}} instead of {{poll}} to dead-wait on the second one if the first replica timed out, while in {{ScannerCallableWithReplicas#call}} we still use {{ResultBoundedCompletionService#poll}} with some timeout for the 2nd replica.
> This JIRA aims at discussing whether to unify the logic in these two kinds of caller with region replica and taking action if necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)