Skip to content
Snippets Groups Projects
  • Taka Shinagawa's avatar
    3ab71eb9
    [DOCS] [MINOR] Update for the Hadoop versions table with hadoop-2.6 · 3ab71eb9
    Taka Shinagawa authored
    Updated the doc for the hadoop-2.6 profile, which is new to Spark 1.4
    
    Author: Taka Shinagawa <taka.epsilon@gmail.com>
    
    Closes #6450 from mrt/docfix2 and squashes the following commits:
    
    db1c43b [Taka Shinagawa] Updated the hadoop versions for hadoop-2.6 profile
    323710e [Taka Shinagawa] The hadoop-2.6 profile is added to the Hadoop versions table
    3ab71eb9
    History
    [DOCS] [MINOR] Update for the Hadoop versions table with hadoop-2.6
    Taka Shinagawa authored
    Updated the doc for the hadoop-2.6 profile, which is new to Spark 1.4
    
    Author: Taka Shinagawa <taka.epsilon@gmail.com>
    
    Closes #6450 from mrt/docfix2 and squashes the following commits:
    
    db1c43b [Taka Shinagawa] Updated the hadoop versions for hadoop-2.6 profile
    323710e [Taka Shinagawa] The hadoop-2.6 profile is added to the Hadoop versions table
building-spark.md 10.99 KiB
layout: global
title: Building Spark
redirect_from: "building-with-maven.html"
  • This will become a table of contents (this text will be scraped). {:toc}

Building Spark using Maven requires Maven 3.0.4 or newer and Java 6+.

Note: Building Spark with Java 7 or later can create JAR files that may not be readable with early versions of Java 6, due to the large number of files in the JAR archive. Build with Java 6 if this is an issue for your deployment.

Building with build/mvn

Spark now comes packaged with a self-contained Maven installation to ease building and deployment of Spark from source located under the build/ directory. This script will automatically download and setup all necessary build requirements (Maven, Scala, and Zinc) locally within the build/ directory itself. It honors any mvn binary if present already, however, will pull down its own copy of Scala and Zinc regardless to ensure proper version requirements are met. build/mvn execution acts as a pass through to the mvn call allowing easy transition from previous build methods. As an example, one can build a version of Spark as follows:

{% highlight bash %} build/mvn -Pyarn -Phadoop-2.4 -Dhadoop.version=2.4.0 -DskipTests clean package {% endhighlight %}

Other build examples can be found below.

Note: When building on an encrypted filesystem (if your home directory is encrypted, for example), then the Spark build might fail with a "Filename too long" error. As a workaround, add the following in the configuration args of the scala-maven-plugin in the project pom.xml:

<arg>-Xmax-classfile-name</arg>
<arg>128</arg>

and in project/SparkBuild.scala add:

scalacOptions in Compile ++= Seq("-Xmax-classfile-name", "128"),

to the sharedSettings val. See also this PR if you are unsure of where to add these lines.

Building a Runnable Distribution

To create a Spark distribution like those distributed by the Spark Downloads page, and that is laid out so as to be runnable, use make-distribution.sh in the project root directory. It can be configured with Maven profile settings and so on like the direct Maven build. Example:

./make-distribution.sh --name custom-spark --tgz -Phadoop-2.4 -Pyarn

For more information on usage, run ./make-distribution.sh --help

Setting up Maven's Memory Usage

You'll need to configure Maven to use more memory than usual by setting MAVEN_OPTS. We recommend the following settings:

{% highlight bash %} export MAVEN_OPTS="-Xmx2g -XX:MaxPermSize=512M -XX:ReservedCodeCacheSize=512m" {% endhighlight %}

If you don't run this, you may see errors like the following:

[INFO] Compiling 203 Scala sources and 9 Java sources to /Users/me/Development/spark/core/target/scala-{{site.SCALA_BINARY_VERSION}}/classes...
[ERROR] PermGen space -> [Help 1]

[INFO] Compiling 203 Scala sources and 9 Java sources to /Users/me/Development/spark/core/target/scala-{{site.SCALA_BINARY_VERSION}}/classes...
[ERROR] Java heap space -> [Help 1]

You can fix this by setting the MAVEN_OPTS variable as discussed before.

Note:

  • For Java 8 and above this step is not required.
  • If using build/mvn and MAVEN_OPTS were not already set, the script will automate this for you.

Specifying the Hadoop Version

Because HDFS is not protocol-compatible across versions, if you want to read from HDFS, you'll need to build Spark against the specific HDFS version in your environment. You can do this through the "hadoop.version" property. If unset, Spark will build against Hadoop 2.2.0 by default. Note that certain build profiles are required for particular Hadoop versions:

Hadoop version Profile required
1.x to 2.1.x hadoop-1
2.2.x hadoop-2.2
2.3.x hadoop-2.3
2.4.x hadoop-2.4
2.6.x and later 2.x hadoop-2.6

For Apache Hadoop versions 1.x, Cloudera CDH "mr1" distributions, and other Hadoop versions without YARN, use:

{% highlight bash %}

Apache Hadoop 1.2.1

mvn -Dhadoop.version=1.2.1 -Phadoop-1 -DskipTests clean package

Cloudera CDH 4.2.0 with MapReduce v1

mvn -Dhadoop.version=2.0.0-mr1-cdh4.2.0 -Phadoop-1 -DskipTests clean package {% endhighlight %}

You can enable the "yarn" profile and optionally set the "yarn.version" property if it is different from "hadoop.version". Spark only supports YARN versions 2.2.0 and later.

Examples:

{% highlight bash %}

Apache Hadoop 2.2.X

mvn -Pyarn -Phadoop-2.2 -DskipTests clean package

Apache Hadoop 2.3.X