[MESOS-1711] Create method for users to identify HDFS compatible protocols in fetcher.cpp

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.19.1
• Fix Version/s: 0.22.0
• Labels: fetcher hadoop hdfs

Environment

All

• Target Version/s: 0.22.0
• Assignee: Ankur Chauhan
• Reporter: John Omernik
• Shepherd: Adam B
• Created: 18/Aug/14 12:57
• Updated: 26/Apr/17 16:52
• Resolved: 06/Nov/14 00:34

Description

In fetcher.cpp, the code to get the Mesos packages uses a hard coded list of protocols to determine if the Hadoop copytoLocal method is used or if another method (such as standard filecopy). This limits the addition of new protocols that are HDFS compatible until the next release of Mesos. Tachyon Filesystem (tachyonfs://), MapR FS (maprfs://) and glusterfs:// are three examples that could make use of this.

Instead of just adding those file systems in the hard coded list, I recommend following the lead of the Tachyon Project. In tachyon-0.6.0-SNAPSHOT, they have added an environment variable of allowed hdfs compatible protocols. This comma-separated list allows the user/admin to specify which protocols are HDFS compatible, without hard coding it in the fetcher.cpp.

I don't have access to the Tachyon issues list for linking, but the code is on line 75 of

https://github.com/amplab/tachyon/blob/master/core/src/main/java/tachyon/UnderFileSystem.java

Issue Links

• relates to: MESOS-4375 Allow schemes in HDFS URI fetcher plugin to be configurable.