Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 31 Jul 2017 07:39:00 +0000 (UTC)
From: "Zheng Hu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13091104.1501486611000.49239.1501486740559@Atlassian.JIRA>
In-Reply-To: <JIRA.13091104.1501486611000@Atlassian.JIRA>
References: <JIRA.13091104.1501486611000@Atlassian.JIRA> <JIRA.13091104.1501486611819@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-18484) VerifyRep by snapshot  does not work
 when Yarn / SourceHBase / PeerHBase located in three different clusters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 31 Jul 2017 07:39:05 -0000


     [ https://issues.apache.org/jira/browse/HBASE-18484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zheng Hu updated HBASE-18484:
-----------------------------
    Summary: VerifyRep by snapshot  does not work when Yarn / SourceHBase / PeerHBase located in three different clusters  (was: VerifyRep by snapshot  does not work when Yarn / SourceHBase / PeerHBase located in three different cluster )

> VerifyRep by snapshot  does not work when Yarn / SourceHBase / PeerHBase located in three different 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
>
> 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
(v6.4.14#64029)