[
https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167671#comment-17167671
]
Anoop Sam John commented on HBASE-18070:
----------------------------------------
Was thinking on this and got to same statement as Andy said above. Its just
like client side meta location cache which can be wrong. Even in a double
assign kind of issue, the meta cache also can cause this issue today. Thought
of n/w partition. But all such possible issues, even today it might happen.
Also we will use the replica reads only for the region location right? Not for
other stuff like the table state/NS data etc.
I think then we are good.
Will wait for the design doc [~huaxiangsun]
> Enable memstore replication for meta replica
> --------------------------------------------
>
> Key: HBASE-18070
> URL: https://issues.apache.org/jira/browse/HBASE-18070
> Project: HBase
> Issue Type: New Feature
> Reporter: Hua Xiang
> Assignee: Huaxiang Sun
> Priority: Major
>
> Based on the current doc, memstore replication is not enabled for meta
> replica. Memstore replication will be a good improvement for meta replica.
> Create jira to track this effort (feasibility, design, implementation, etc).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
