[
https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233790#comment-17233790
]
Michael Stack commented on HBASE-18070:
---------------------------------------
{quote}If you think you have something that can not be spoken out publicly then
I'm fine with a zoom call.
{quote}
Suggested it because I thought we'd agreed to go to face-to-face if a problem
communicating arose post Yu Li's help. That seems to be what is going on here
(and you put a -1 on top of it to boot).
On [https://github.com/apache/hbase/pull/2644], when I went there, I was late
to the game, trying to help clean up some crossed-wires around resolved Jira
but open PRs (or other way round). All conversations were 'resolved'. Your
'request changes' I presumed a vestige of a resolved conversation. Seemed like
minor stuff. No intentional dissing on my part. I can reopen if you want.
Suggest you not get hung up on my representation. There is a design here with a
long-standing description of what the work here is about and you have helped
review the patches that comprise this work. Just use these instead.
> 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)
