[jira] [Reopened] (HBASE-8304) Bulkload fails to remove files if fs.default.name / fs.defaultFS is configured without default port

["haosdent (JIRA)" <ji...@apache.org>]

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

haosdent reopened HBASE-8304:
-----------------------------


Attach 0.94 and 0.96 patchs.

> Bulkload fails to remove files if fs.default.name / fs.defaultFS is configured without default port
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8304
>                 URL: https://issues.apache.org/jira/browse/HBASE-8304
>             Project: HBase
>          Issue Type: Bug
>          Components: HFile, regionserver
>    Affects Versions: 0.94.5
>            Reporter: Raymond Liu
>            Assignee: haosdent
>              Labels: bulkloader
>             Fix For: 0.98.1, 0.99.0
>
>         Attachments: 8304-v4.patch, HBASE-8304-v2.patch, HBASE-8304-v3.patch, HBASE-8304.patch
>
>
> When fs.default.name or fs.defaultFS in hadoop core-site.xml is configured as hdfs://ip, and hbase.rootdir is configured as hdfs://ip:port/hbaserootdir where port is the hdfs namenode's default port. the bulkload operation will not remove the file in bulk output dir. Store::bulkLoadHfile will think hdfs:://ip and hdfs:://ip:port as different filesystem and go with copy approaching instead of rename.
> The root cause is that hbase master will rewrite fs.default.name/fs.defaultFS according to hbase.rootdir when regionserver started, thus, dest fs uri from the hregion will not matching src fs uri passed from client.
> any suggestion what is the best approaching to fix this issue? 
> I kind of think that we could check for default port if src uri come without port info.



--
This message was sent by Atlassian JIRA
(v6.2#6252)