Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 21 Mar 2016 21:30:25 +0000 (UTC)
From: "Geoffrey Jacoby (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12952212.1458595784000.10115.1458595825701@Atlassian.JIRA>
In-Reply-To: <JIRA.12952212.1458595784000@Atlassian.JIRA>
References: <JIRA.12952212.1458595784000@Atlassian.JIRA>
 <JIRA.12952212.1458595784745@arcas>
Subject: [jira] [Created] (HBASE-15507) Online modification of enabled
 ReplicationPeerConfig
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Geoffrey Jacoby created HBASE-15507:
---------------------------------------

             Summary: 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: 1.2.0, 2.0.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)