[
https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235065#comment-17235065
]
Duo Zhang commented on HBASE-18070:
-----------------------------------
Thank you [~huaxiangsun] , I agree with most of your answers. The only thing is
that I do not think the current solution can not provide HA, if the ‘HA’ here
is something similar to the old read replicas feature. Client has built in
retries so if we fail to request a replica then we will go to another one,
unless all the replicas are down. But if all the replicas are down, the old
read replicas feature can not solve the problem either.
In general I think the approach here is a very good improvement. Thank you for
your great work on the this issue.
But sorry I can not change my veto because the problem here is that I can not
confirm whether stack is on the same page with us. And since he still refused
to answer my questions, after pointing me to a 30 minutes YouTube video, this
time he pointed me to a bunch of design docs, I do not think I can change my
veto in a short time then. I’m on a business trip so not all the time I could
access google related sites. And I do not have enough time to read and watch so
many materials, it may cost a month or so for me to finish the reading, and
then I still need to ask questions to him, if he still refuses to answer then
maybe we can not get this in within this year...
Thanks.
> 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)
