Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 Dec 2015 22:07:47 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12916266.1448482996000.59734.1450390067133@Atlassian.JIRA>
In-Reply-To: <JIRA.12916266.1448482996000@Atlassian.JIRA>
References: <JIRA.12916266.1448482996000@Atlassian.JIRA>
 <JIRA.12916266.1448482996524@arcas>
Subject: [jira] [Updated] (HBASE-14886) ReplicationAdmin does not use full
 peer configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-14886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-14886:
--------------------------------
         Assignee:     (was: Gary Helmling)
    Fix Version/s:     (was: 1.3.0)
                       (was: 1.2.0)
                       (was: 2.0.0)

removing fix versions since this was resolved as duplicate.

> ReplicationAdmin does not use full peer configuration
> -----------------------------------------------------
>
>                 Key: HBASE-14886
>                 URL: https://issues.apache.org/jira/browse/HBASE-14886
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Gary Helmling
>            Priority: Critical
>         Attachments: hbase-14886-v1.patch, hbase-14886-v2.patch, hbase-14886.patch
>
>
> In {{listValidReplicationPeers()}}, we're creating the peer {{Configuration}} based on the source connection configuration and simply applying the peer ZK cluster key.  This causes any additional properties present in the {{ReplicationPeerConfig}} configuration to not be applied.
> We should instead be using the configuration returned by {{ReplicationPeers.getPeerConf()}}, which we already call in that method.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)