[
https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235073#comment-17235073
]
Duo Zhang commented on HBASE-18070:
-----------------------------------
{quote}
I think different. The 'current problem' is the interaction between you and I
and not to be found 'here' in this JIRA. This is my last comment here in my
attempt at moving what I see as the problem out of this JIRA.
{quote}
You are free to think different and I'm open on how to solve the problem, but
this is not related to the concerns here right?
{quote}
On your questions, I'd have referred you to the design doc but I see Huaxiang
Sun has answered in-line (Thanks Huaxiang Sun ).
{quote}
Let me explain more. For a big and important change on a feature branch, it is
not likely for me to review all the details. So it is very important that I
need to make sure that all have the same understanding on the problem and also
reach an agreement on how to solve the problem. I think the latter one is not a
problem as the sub tasks can tell us the things. Here the problem is for the
former one. The difficulty we met on how to confirm the approach here can work
well made think that we have different opinion on what can be solved by this
problem and what can be solved by the old read replicas problem. This is a very
big problem for me. If we can not even agree on this fundamental stuff then I
do not think I should allow the code to go into the main code base, as it may
contain unexpected code. That's why I want to double check here if we are still
on the same page, that's why I asked the 4 technical questions above.
If we can confirm that we do not have big differences on the 4 question above,
then I think the problem should be a bad communication(now due to the recent
replies gotten from you I think this is more likely to be the problem but I
still need to get the answers of the technical part). Then I will change my
veto to a big +1 as this is really a good improvement and we also want to try
it in our producation. For the bad communication problem we can work it
separately as it is not related to the issue here.
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)
