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

Adrian Muraru commented on HBASE-20140:
---------------------------------------

[~yuzhih...@gmail.com]
{quote}Did you find the issue using the above config ?
{quote}
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 
insteaf of actual hbase.rootDir

A bit of an edge case, but still important
{quote}If so, is there any other place where similar change should be made ?
{quote}
There are probably other places, yes, but to be honest I limited the patch to 
HFile code to avoid extra side-effects.

> 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
>            Reporter: Adrian Muraru
>            Assignee: Adrian Muraru
>            Priority: Minor
>         Attachments: 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}}



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

Reply via email to