[
https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232872#comment-17232872
]
Andrew Kyle Purtell commented on HBASE-18070:
---------------------------------------------
On the merge thread [~stack] asked for more time to resolve the concerns. I'm
leaving the fix version at 2.5.0 but if there can be agreement here soon we can
move it back in.
In my opinion the difference in opinion comes down to what is the client's
policy for choosing a replica if there are meta replicas available. The client
can try the primary first, then fall back to a replica; that is one reasonable
policy. Or, the client can choose any replica at random, that is another
reasonable policy. Perhaps we can agree on a timeline to implementation of both
policies that allows for the merge of this feature into 2.4 to proceed.
> 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: Critical
> Fix For: 3.0.0-alpha-1, HBASE-18070, HBASE-18070.branch-2, 2.5.0
>
>
> 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)
