[
https://issues.apache.org/jira/browse/HBASE-26204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404391#comment-17404391
]
Hudson commented on HBASE-26204:
--------------------------------
Results for branch master
[build #375 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/375/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/375/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/375/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/375/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> VerifyReplication should obtain token for peerQuorumAddress too
> ---------------------------------------------------------------
>
> Key: HBASE-26204
> URL: https://issues.apache.org/jira/browse/HBASE-26204
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha-1
> Reporter: Shinya Yoshida
> Assignee: Shinya Yoshida
> Priority: Major
> Fix For: 3.0.0-alpha-2
>
>
> VerifyReplication accepts peerQuorumAddress itself via command parameter
> instead of getting it from peerid of source cluster.
> [https://github.com/apache/hbase/commit/b322d0a3e552dc228893408161fd3fb20f6b8bf1#diff-0307194efcf6a3ad4a4d73bd4b6ef34a9be5c436c8e970ca97fa146b2f0aa486]
> https://issues.apache.org/jira/browse/HBASE-21201
> {code:java}
> if (peerId != null) {
> assert peerConfigPair != null;
> Configuration peerClusterConf = peerConfigPair.getSecond();
> // Obtain the auth token from peer cluster
> TableMapReduceUtil.initCredentialsForCluster(job, peerClusterConf);
> }
> {code}
> In this patch, credential for job is obtained when peerid is provided only.
> Thus we cannot get the benefit of HBASE-21201 for secure hbase cluster as a
> destination.
> {code:java}
> hbase VerifyReplication \
> -D
> verifyrep.peer.hbase.regionserver.kerberos.principal=secure-hbase-b/[email protected]
> \
> -D
> verifyrep.peer.hbase.master.kerberos.principal=secure-hbase-b/[email protected]
> \
> ... \
>
> secure-hbase-b-1.example.com,secure-hbase-b-2.example.com,secure-hbase-b-3.example.com:2181:/hbase-b
> \
> table
> {code}
> Assume this execution, VerifyReplication should obtain token from
> secure-hbase-b-1.example.com,secure-hbase-b-2.example.com,secure-hbase-b-3.example.com:2181:/hbase-b
> using hbase.regionserver.kerberos.principal=secure-hbase-b/[email protected]
> and hbase.master.kerberos.principal=secure-hbase-b/[email protected], so that
> VerifyReplication mapper can scan from the secure cluster B.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
