[HADOOP-12304] Applications using FileContext fail with the default file system configured to be wasb/s3/etc.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0, 2.7.1
• Fix Version/s: 2.8.0, 2.7.2, 3.0.0-alpha1
• Component/s: fs
• Labels: 2.7.2-candidate
• Target Version/s: 2.7.2
• Hadoop Flags: Reviewed
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 05/Aug/15 19:43
• Updated: 02/Dec/16 00:36
• Resolved: 05/Aug/15 22:10

Description

HADOOP-11618 fixed a bug with DelegateToFileSystem using the wrong default port. As a side effect of this patch, file path URLs that previously had no port now insert :0 for the port, as per the default implementation of FileSystem#getDefaultPort. At runtime, this can cause an application to erroneously try contacting port 0 for a remote blob store service. The connection fails. Ultimately, this renders wasb, s3, and probably custom file system implementations outside the Hadoop source tree completely unusable as the default file system.

Issue Links

• breaks: HADOOP-12991 Conflicting default ports in DelegateToFileSystem
• is broken by: HADOOP-11618 DelegateToFileSystem erroneously uses default FS's port in constructor
• is required by: HADOOP-11262 Enable YARN to use S3A