hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8304) Bulkload fail to remove files if fs.default.name / fs.defaultFS is configured without default port.
Date Tue, 04 Mar 2014 22:57:42 GMT

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

Ted Yu commented on HBASE-8304:

You can compare https://builds.apache.org/job/PreCommit-HBASE-Build/8881/artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
with https://builds.apache.org/job/PreCommit-HBASE-Build/8880/artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
to find which new findbugs warning was introduced.

> Bulkload fail 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
>         Attachments: HBASE-8304-v2.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

View raw message