[
https://issues.apache.org/jira/browse/HBASE-25343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241331#comment-17241331
]
Huaxiang Sun commented on HBASE-25343:
--------------------------------------
Went through the code path about how AsyncSingleRequestRpcRetryingCaller
handles errors and retries, I think in reality, adding logic to try with
another meta replica region after multiple retries (15 as the default) does
not make too much sense. Unless there is something fundamentally wrong, it will
succeed with the selected meta replica region. At the other hand, after 15
retries (after a long time), it would be better to report the failure to the
caller.
I am going to resolve it as unimplemented for now.
> Add HA support on top of Load Balance mode
> ------------------------------------------
>
> Key: HBASE-25343
> URL: https://issues.apache.org/jira/browse/HBASE-25343
> Project: HBase
> Issue Type: Sub-task
> Components: meta replicas
> Affects Versions: 2.4.0
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
> Fix For: 2.4.1
>
>
> This is a follow-up enhancement with Stack, Duo. With the newly introduced
> meta replica LoadBalance mode, if there is something wrong with one of meta
> replica regions, the current logic is that it keeps trying until the meta
> replica region is onlined again or it reports error, i.e, there is no HA at
> LoadBalance mode. HA can be implemented if it reports timeout with one meta
> replica region and tries another meta replica region.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
