[
https://issues.apache.org/jira/browse/HBASE-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178403#comment-15178403
]
Devaraj Das commented on HBASE-15383:
-------------------------------------
The point to note is that responses from secondaries are always flagged as
"stale", even if the secondary does have the latest updates... Without
addressing that, it's not easy to address this jira.
> Load distribute across secondary read replicas for meta
> -------------------------------------------------------
>
> Key: HBASE-15383
> URL: https://issues.apache.org/jira/browse/HBASE-15383
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Ashu Pachauri
> Assignee: Ashu Pachauri
> Fix For: 2.0.0, 1.3.0
>
>
> Right now, we always hit the primary replica for meta and fallback to the
> secondary replicas in case of a timeout. This can hamper performance in
> scenarios where meta becomes a hot region e.g. cluster ramp up..clients
> dropping connections etc.
> It's good to have a load distribution approach on meta's secondary replicas
> with fallback to primary if we read stale data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
