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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.94.5
• Fix Version/s: 0.98.1, 0.99.0
• Component/s: HFile, regionserver
• Labels: bulkloader
• Hadoop Flags: Reviewed
• Assignee: haosdent
• Reporter: Raymond Liu
• Created: 09/Apr/13 08:12
• Updated: 21/Feb/15 23:30
• Resolved: 10/Mar/14 08:17

Description

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.

Issue Links

• is related to: HBASE-10712 Backport HBASE-8304 to 0.94 and 0.96
• relates to: HBASE-9537 completebulkload does 'copy' StoreFiles instead of 'cut'