[
https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176155#comment-17176155
]
Duo Zhang commented on HBASE-18070:
-----------------------------------
I think HBASE-15867 has a conflict with the approach here. In HBASE-15867, we
are trying to make use of the trick that, we will not track the WAL files
created by MetaWALProvider. But here, we need to track them as we need to
replicate them...
Maybe we could find a more light-weighted way to do memstore replication? In
general, we do not need to catch up all the edits right? A flush can fix all
the inconsistency between replicas, so maybe we do not need to make use of the
complicated replication framework? Just issue a flush request when the lag
between different replicas are too big.
Just brainstorming.
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: 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)
