Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 00A7D200C78 for ; Thu, 18 May 2017 20:38:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F331E160BB5; Thu, 18 May 2017 18:38:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 45E96160B9D for ; Thu, 18 May 2017 20:38:07 +0200 (CEST) Received: (qmail 29515 invoked by uid 500); 18 May 2017 18:38:06 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 29504 invoked by uid 99); 18 May 2017 18:38:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2017 18:38:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 0B8BFCD978 for ; Thu, 18 May 2017 18:38:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 8OViAORoS4Kz for ; Thu, 18 May 2017 18:38:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 245965F3FE for ; Thu, 18 May 2017 18:38:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5032AE01A8 for ; Thu, 18 May 2017 18:38:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 0C75921B56 for ; Thu, 18 May 2017 18:38:04 +0000 (UTC) Date: Thu, 18 May 2017 18:38:04 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18070) Enable memstore replication for meta replica MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 18 May 2017 18:38:08 -0000 [ https://issues.apache.org/jira/browse/HBASE-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016224#comment-16016224 ] Enis Soztutar commented on HBASE-18070: --------------------------------------- In replication, updates to system tables are filtered out before being given to the replication endpoints. Since "region replica replication" is just a replication endpoint, at this point it is not even receiving the edits for meta. Changing this should not be that hard, the only thing is that the replication source has to be careful to still filter out these edits for regular replication endpoints. > 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: huaxiang sun > Assignee: huaxiang sun > > 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 (v6.3.15#6346)