[
https://issues.apache.org/jira/browse/HBASE-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-16172:
--------------------------
Assignee: Ted Yu (was: Yu Li)
Re-assign to Ted since already some work done (and thanks [~chenheng] for
follow up).
Checking the patch it modifies {{RpcRetryingCallerWithReadReplicas}} to follow
the same way with {{ScannerCallableWithReadReplicas}}, so there won't be any
more dead-wait. I think the patch look good although opposite to what proposed
in HBASE-16132 (making ScannerCallableWithReadReplicas follow the way of
RpcRetryingCallerWithReadReplicas)
So, my +1 for the patch, and thanks Ted to take this up.
> 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
>
>
> 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)
