Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5EBE10A1D for ; Mon, 10 Mar 2014 08:18:46 +0000 (UTC) Received: (qmail 61909 invoked by uid 500); 10 Mar 2014 08:18:46 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 61872 invoked by uid 500); 10 Mar 2014 08:18:45 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 61858 invoked by uid 99); 10 Mar 2014 08:18:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 08:18:45 +0000 Date: Mon, 10 Mar 2014 08:18:45 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-8304) Bulkload fails to remove files if fs.default.name / fs.defaultFS is configured without default port MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-8304. ----------------------------------- Resolution: Fixed Fix Version/s: (was: 0.94.18) (was: 0.96.2) Re-resolving. These changes have already been committed for more than one day to trunk and 0.98. When I resolved this the last comment was 0.96 or 0.94 patches might come "later" at some unspecified time. So now it's done. Leave this issue resolved and reopen exactly when needed at commit time to 0.96 and 0.94, or file backport JIRAs. Leaving issues open after commit is bad practice for two reasons: 1. JIRA searches return incorrect results, 2. JIRA state becomes out of sync with repository (commit) state. Thanks in advance for your cooperation. > 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: 0.94-8304.patch, 0.96-8304.patch, 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)