[MESOS-700] more efficient distribution of frameworks via HDFS

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.13.0, 0.14.0, 0.15.0
• Component/s: framework

Environment

general

• Assignee: Unassigned
• Reporter: Du Li
• Created: 19/Sep/13 22:06
• Updated: 02/Jul/15 18:43
• Resolved: 16/May/14 23:19

Description

I was exploring the latest code (0.15.0) at https://github.com/apache/mesos to test the tgz distribution of frameworks. Take spark for example. I created a tgz of spark binary and put it on HDFS. After a job is submitted, it is decomposed into many tasks. For each task, the assigned mesos slave downloads the tgz from HDFS, unzips it, and executes some script to launch the task. This seems very wasteful and unnecessary.

Does the following suggestion make sense? When a spark job is submitted, the spark/mesos master calculates a checksum or something the like for the tgz distribution. Then the checksum is sent to the slaves when tasks are assigned. If the same file has already been downloaded/unzipped, a slave directly launches the task. This way the tgz is processed at most once for each job (which may have thousands of tasks). The aggregated saving would be tremendous.

Issue Links

• duplicates: MESOS-336 Mesos slave should cache executors
• is related to: MESOS-336 Mesos slave should cache executors