Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3955E19A4F for ; Thu, 31 Mar 2016 18:57:26 +0000 (UTC) Received: (qmail 91565 invoked by uid 500); 31 Mar 2016 18:57:26 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 91514 invoked by uid 500); 31 Mar 2016 18:57:26 -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 91478 invoked by uid 99); 31 Mar 2016 18:57:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2016 18:57:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A50992C1F69 for ; Thu, 31 Mar 2016 18:57:25 +0000 (UTC) Date: Thu, 31 Mar 2016 18:57:25 +0000 (UTC) From: "Geoffrey Jacoby (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work started] (HBASE-15507) Online modification of enabled ReplicationPeerConfig MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-15507 started by Geoffrey Jacoby. ----------------------------------------------- > Online modification of enabled ReplicationPeerConfig > ---------------------------------------------------- > > Key: HBASE-15507 > URL: https://issues.apache.org/jira/browse/HBASE-15507 > Project: HBase > Issue Type: Improvement > Components: Replication > Affects Versions: 2.0.0, 1.2.0, 1.3.0 > Reporter: Geoffrey Jacoby > Assignee: Geoffrey Jacoby > > It's currently possible to update the table CFs for a replication peer while it's running, but not the peer configuration or data maps introduced as part of custom replication endpoints in HBASE-11367. > This means that if you have a custom endpoint that depends on some configuration parameter, you have to remove the peer and recreate it in order to change the param. In some use cases that's not possible without risking data loss. > HBASE-11393, which will consolidate tableCFs in the same znode as the rest of ReplicationPeerConfig, may help here, but with or without it it still seems like there needs to be further work to add update config/data API support to ReplicationAdmin and a callback mechanism to notify the endpoints of config parameter changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)