You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/06/08 12:51:21 UTC
[jira] [Commented] (HBASE-15769) Perform validation on cluster key
for add_peer
[ https://issues.apache.org/jira/browse/HBASE-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320485#comment-15320485 ]
Hudson commented on HBASE-15769:
--------------------------------
FAILURE: Integrated in HBase-0.98-matrix #353 (See [https://builds.apache.org/job/HBase-0.98-matrix/353/])
HBASE-15769 Perform validation on cluster key for add_peer (Matt (apurtell: rev 458378d7089a18b325a35c4c99ca15272fb033b4)
* hbase-shell/src/main/ruby/shell/commands/add_peer.rb
* hbase-common/src/test/java/org/apache/hadoop/hbase/zookeeper/TestZKConfig.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKConfig.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationStateBasic.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java
> Perform validation on cluster key for add_peer
> ----------------------------------------------
>
> Key: HBASE-15769
> URL: https://issues.apache.org/jira/browse/HBASE-15769
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Matt Warhaftig
> Priority: Minor
> Fix For: 2.0.0, 1.4.0, 0.98.20
>
> Attachments: hbase-15769-v1.patch, hbase-15769-v2.patch
>
>
> [~pateljaymin] reported the following.
> In hbase cluster, adding a peer for replication, incorrectly defined zookeeper znode does not fail new peer creation. However, replication breaks down.
> For example,
> below string incorrectly defines zookeeper znode as "hbase" instead of "/hbase"...
> {code}
> > add_peer '1', "host1.com,host2.com,host3.com:2181:hbase
> {code}
> This left replication broken, even after we dropped and added a new correct entry for the peer.
> It wasn't until we bounced the cluster that the issue was fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)