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 B9C18200B99 for ; Tue, 30 Aug 2016 14:05:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B8685160AA8; Tue, 30 Aug 2016 12:05:22 +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 0144A160ACC for ; Tue, 30 Aug 2016 14:05:21 +0200 (CEST) Received: (qmail 4877 invoked by uid 500); 30 Aug 2016 12:05:21 -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 4618 invoked by uid 99); 30 Aug 2016 12:05:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2016 12:05:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E347F2C014C for ; Tue, 30 Aug 2016 12:05:20 +0000 (UTC) Date: Tue, 30 Aug 2016 12:05:20 +0000 (UTC) From: "Guanghao Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-16447) Replication by namespaces config in peer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 30 Aug 2016 12:05:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-16447: ----------------------------------- Description: Now we only config table cfs in peer. But in our production cluster, there are a dozen of namespace and every namespace has dozens of tables. It was complicated to config all table cfs in peer. For some namespace, it need replication all tables to other slave cluster. It will be easy to config if we support replication by namespace. Suggestions and discussions are welcomed. Review board: https://reviews.apache.org/r/51521/ was:Now we only config table cfs in peer. But in our production cluster, there are a dozen of namespace and every namespace has dozens of tables. It was complicated to config all table cfs in peer. For some namespace, it need replication all tables to other slave cluster. It will be easy to config if we support replication by namespace. Suggestions and discussions are welcomed. > Replication by namespaces config in peer > ---------------------------------------- > > Key: HBASE-16447 > URL: https://issues.apache.org/jira/browse/HBASE-16447 > Project: HBase > Issue Type: New Feature > Components: Replication > Affects Versions: 2.0.0 > Reporter: Guanghao Zhang > Assignee: Guanghao Zhang > Attachments: HBASE-16447-v1.patch > > > Now we only config table cfs in peer. But in our production cluster, there are a dozen of namespace and every namespace has dozens of tables. It was complicated to config all table cfs in peer. For some namespace, it need replication all tables to other slave cluster. It will be easy to config if we support replication by namespace. Suggestions and discussions are welcomed. > Review board: https://reviews.apache.org/r/51521/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)