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 C94F519073 for ; Wed, 16 Mar 2016 23:33:33 +0000 (UTC) Received: (qmail 4343 invoked by uid 500); 16 Mar 2016 23:33:33 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 4296 invoked by uid 500); 16 Mar 2016 23:33:33 -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 4270 invoked by uid 99); 16 Mar 2016 23:33:33 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Mar 2016 23:33:33 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 6F8852C1F54 for ; Wed, 16 Mar 2016 23:33:33 +0000 (UTC) Date: Wed, 16 Mar 2016 23:33:33 +0000 (UTC) From: "Geoffrey Jacoby (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-12940) Expose listPeerConfigs and getPeerConfig to the HBase shell 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-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198414#comment-15198414 ] Geoffrey Jacoby commented on HBASE-12940: ----------------------------------------- Yes, I noticed those, and they concerned me at first. On a deeper look though, these appear to be coming from HBase trying to actually set up replication with remote clusters that aren't actually there. ReplicationPeersZKImpl assumes that the remote ZooKeeper quorum it's given as the cluster key is a real thing that it can immediately go talk to. But none of the quorums mentioned in the tests exist, so the watcher threads on the minicluster are unhappy. But that doesn't stop us from verifying that the replication_admin wrapper and ReplicationAdmin class are successfully putting data into _our_ minicluster ZK instance, and able to get it back out again. There are also some exceptions related to an unneeded table the existing test setup creates, and I filed a separate JIRA, HBASE-15472, to take care of that one. > Expose listPeerConfigs and getPeerConfig to the HBase shell > ----------------------------------------------------------- > > Key: HBASE-12940 > URL: https://issues.apache.org/jira/browse/HBASE-12940 > Project: HBase > Issue Type: Bug > Components: shell > Reporter: Kevin Risden > Assignee: Geoffrey Jacoby > Attachments: HBASE-12940-v1.patch, HBASE-12940.patch > > > In HBASE-12867 found that listPeerConfigs and getPeerConfig from ReplicationAdmin are not exposed to the HBase shell. This makes looking at details for custom replication endpoints and testing of add_peer from HBASE-12867 impossible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)