You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nihal Jain (JIRA)" <ji...@apache.org> on 2019/01/17 05:57:00 UTC

[jira] [Updated] (HBASE-20140) HRegion FileSystem should be instantiated from hbase rootDir not default

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

Nihal Jain updated HBASE-20140:
-------------------------------
    Labels: s3  (was: )

> HRegion FileSystem should be instantiated from hbase rootDir not default
> ------------------------------------------------------------------------
>
>                 Key: HBASE-20140
>                 URL: https://issues.apache.org/jira/browse/HBASE-20140
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 3.0.0, 2.0.2, 1.4.7
>            Reporter: Adrian Muraru
>            Assignee: Adrian Muraru
>            Priority: Minor
>              Labels: s3
>         Attachments: HBASE-20140.branch-1.v01.patch, HBASE-20140.branch-2.v01.patch, HBASE-20140.v01.patch
>
>
> HRegion fs initialization is done based on HDFS default {{fs.defaultFs}} instead of {{hbase.rootdir}}
> This is breaking in cases where the {{fs.defaultFs}} is set to a different  filesystem than the one set in fully qualified {{hbase.rootdir}}
>  
> The usecase is the following: running an yarn cluster with `fs.defaultFs` set to local HDFS and running a MR job over HBase Snapshots setting the {{hbase.rootDir}} to external S3 Filesystem (fully qualified). In this case when the regions are actually cold loaded in map tasks the defaultFs is used instead of actual hbase.rootDir



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)