You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ashish Singhi (JIRA)" <ji...@apache.org> on 2016/02/12 11:09:18 UTC

[jira] [Commented] (HBASE-14866) VerifyReplication should use peer configuration in peer connection

    [ https://issues.apache.org/jira/browse/HBASE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144353#comment-15144353 ] 

Ashish Singhi commented on HBASE-14866:
---------------------------------------

[~ghelmling], can you please add a release note for this or better can we document this in our book ?

> VerifyReplication should use peer configuration in peer connection
> ------------------------------------------------------------------
>
>                 Key: HBASE-14866
>                 URL: https://issues.apache.org/jira/browse/HBASE-14866
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
>         Attachments: HBASE-14866-0.98.patch, HBASE-14866.patch, HBASE-14866_v1.patch, hbase-14866-branch-1-v1.patch, hbase-14866-v4.patch, hbase-14866-v5.patch, hbase-14866-v6.patch, hbase-14866_v2.patch, hbase-14866_v3.patch
>
>
> VerifyReplication uses the replication peer's configuration to construct the ZooKeeper quorum address for the peer connection.  However, other configuration properties in the peer's configuration are dropped.  It should merge all configuration properties from the {{ReplicationPeerConfig}} when creating the peer connection and obtaining a credentials for the peer cluster.



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