[
https://issues.apache.org/jira/browse/HBASE-18484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766102#comment-16766102
]
Hudson commented on HBASE-18484:
--------------------------------
Results for branch branch-2.1
[build #857 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/857/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/857//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/857//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/857//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> VerifyRep by snapshot does not work when Yarn / SourceHBase / PeerHBase
> located in different HDFS clusters
> -----------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18484
> URL: https://issues.apache.org/jira/browse/HBASE-18484
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 2.0.0-alpha-1
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4
>
> Attachments: HBASE-18484.v1.patch, HBASE-18484.v2.patch,
> HBASE-18484.v3.patch
>
>
> As HBASE-16466 commented.
> Seems like that when source hbase cluster / peer hbase cluster / yarn cluster
> locate in three different HDFS cluster , it has one problem.
> when restoring the snapshot into tmpdir , we need to create region by
> following code (HRegion#createHRegion)
> {code}
> public static HRegion createHRegion(final HRegionInfo info, final Path
> rootDir,
> final Configuration conf, final TableDescriptor hTableDescriptor,
> final WAL wal, final boolean initialize)
> throws IOException {
> LOG.info("creating HRegion " + info.getTable().getNameAsString()
> + " HTD == " + hTableDescriptor + " RootDir = " + rootDir +
> " Table name == " + info.getTable().getNameAsString());
> FileSystem fs = FileSystem.get(conf);
> <------------------- Here our code use fs.defaultFs configuration to create
> region.
> Path tableDir = FSUtils.getTableDir(rootDir, info.getTable());
> HRegionFileSystem.createRegionOnFileSystem(conf, fs, tableDir, info);
> HRegion region = HRegion.newHRegion(tableDir, wal, fs, conf, info,
> hTableDescriptor, null);
> if (initialize) region.initialize(null);
> return region;
> }
> {code}
> When source cluster & peer cluster locate in two difference file systems ,
> then their fs.defaultFs should be difference, so at least one cluster will
> fail when restore snapshot into tmpdir . after I added the following fix, it
> works fine for me.
> {code}
> -FileSystem fs = FileSystem.get(conf);
> +FileSystem fs = rootDir.getFileSystem(conf);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
